that goes for macblog and iosblog too. i have to navigate to https://buyersguide.macrumors.com/ or https://forums.macrumors.com or else i'm just looking at an empty browser. any ideas?
safari 6.0.1
osx 10.8.2
safari 6.0.1
osx 10.8.2
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
No MacRumors front page for me?
- Thread starter txr0ckabilly
- Start date
- Sort by reaction score
It is working for me on the same OS and Safari versions you have. Maybe try clearing the Safari cache.
i reset safari and cleared the cache and still no front page. don't know why this got moved to site and forum feedback. it seems like its a technical issue with the OS and browser to me.... whatever...
I've just got no sidebar, it's below the main content for me... Same computer that I have used before with same screen resolution/browser size.
The same thing was happening to me. I tried switching browsers but it didn't help (I tried Safari and Camino but neither of them would load the front page). I turned off JavaScript and now things are fine.
Thank you for that! I must admit, I thought Javascript was required for login (as with other sites), so I didn't even try turning it off.
Turned off JS and yeah, the sidebar is back to normal. However, this still isn't fixed with it on. An update from the MR team would be appreciated. 
OLDCODGER,
Did turning off JavaScript work for you? If I turn on JavaScript, I get a blank page. Simply turning off JavaScript and reloading the pages works for me. I wasn't sure if it would work for you or not as I don't have Omniweb. I think it is an advertisement with some bad JavaScript, just a guess. I'm not having any problems with the sidebar on my computer.
Mecha
Did turning off JavaScript work for you? If I turn on JavaScript, I get a blank page. Simply turning off JavaScript and reloading the pages works for me. I wasn't sure if it would work for you or not as I don't have Omniweb. I think it is an advertisement with some bad JavaScript, just a guess. I'm not having any problems with the sidebar on my computer.
Mecha
Yes, thanks. I, too, got the blank page on Omniweb and Slimboat - but not Safari (which i hate). I use Omniweb because it allows for page/site specific preferences - on the fly, and sidebar thumbnail tabs.
Hey guys,
Sorry. Didn't realize this was still an issue. I'm downloading Omniweb to see if I can reproduce the issue.
arn
----------
I can't seem to reproduce this on Chrome for iPad or Omniweb.
Can people clarify if it's 100% of the time, or just on some page loads?
Also can you be specific about which versions you are using os/browser?
thanks
arn
Sorry. Didn't realize this was still an issue. I'm downloading Omniweb to see if I can reproduce the issue.
arn
----------
I can't seem to reproduce this on Chrome for iPad or Omniweb.
Can people clarify if it's 100% of the time, or just on some page loads?
Also can you be specific about which versions you are using os/browser?
thanks
arn
I have a similar issue since today (did not happen before). I use Camino 2.1.2 on Tiger, and at random, the page is replaced with a blank page at the end of loading. So I see the correct page for 1/10th of a second, and total whiteness.
If I reload 3-4 times, it might work.
The front page has more problems than the forum pages.
If I turn off JS, no issues.
If I reload 3-4 times, it might work.
The front page has more problems than the forum pages.
If I turn off JS, no issues.
When you get that blank page scroll up and down then back up and see if the page appears.
Arn, I am using Omniweb 5.11.2 on SL 10.6.8.
I get exactly the same issues as reported by blanka, including the fact that forum pages sometimes load properly.
Quitting Javascript solves the problem.
----------
No dice - there are no scroll bars.
I get exactly the same issues as reported by blanka, including the fact that forum pages sometimes load properly.
Quitting Javascript solves the problem.
----------
No dice - there are no scroll bars.
That fixed it, thanks!
Let me know if it happens again. We made another change that shouldn't have affected this, but could have.
arn