Problems with Firefox 5.0.1 website layouts in Lion
After I downloaded Lion, I ran Firefox 5.0.1. Immediately, I noticed significant layout problems in CNN.com and MSNBC.com. And on Facebook, the friends, message, and notification icons at the upper left didn't work. Nor did entering comments to Facebook posts. Even the button that says "View X Comments" in friends' posts didn't work. For comparison, all of them work fine on Safari 5.1.
I rebooted Firefox 5.0.1 with plugins disabled, and still encountered the same problems.
ჩასწორების თარიღი: , ავტორი: mcjanger
გადაწყვეტა შერჩეულია
Websites look wrong
https://support.mozilla.com/en-US/kb/Websites%20look%20wrong
Check and tell if its working.
პასუხის ნახვა სრულად 👍 3ყველა პასუხი (5)
Following up on the problems I reported above, I installed Java for Mac OS 7 (Lion) -- which is not included in the Lion installation. Unfortunately, this did not resolve the problems with Firefox layouts. Putting this out here for those who think Java may be the issue.
ჩასწორების თარიღი: , ავტორი: mcjanger
I am also having problems with Google Mail and Yahoo mail. Buttons are un-selectable and operations just time out. Seems like a major number of issues. In Yahoo mail when trying to check boxes to delete email - the box will not fill with the check. When opening some email all that opens is totally blank. Other email upon opening will download the text of the email (visible) with the timer circling endlessly.
Thanks
Thanks for the post. Have not seen the problem with Google Mail on my end, but I definitely see problems on Google Maps. Cannot toggle between map and satellite view, and location pin does not initialize.
Firefox 5.0.1 is unusable at this point, so I'm using Safari on a temporary basis until hopefully this problem is resolved.
შერჩეული გადაწყვეტა
Websites look wrong
https://support.mozilla.com/en-US/kb/Websites%20look%20wrong
Check and tell if its working.
Solved! The problem - at least on my end - was that the old version was cached. Thanks for the link. (FYI: I never had that problem on earlier Firefox upgrades. It only manifested itself when I upgraded to Lion -- after I had already upgraded to FF 5.0.1 on OS X 10.6.)