Problems with Firefox 3.5

July 1, 2009 8:53 AM

I have found a couple of things on web pages which don't appear correctly for me in Firefox 3.5. Help me work out why.

The two in question are:

http://www.youtube.com/html5 : The video controls don't work, nothing plays. The rest of the page is fine.

The Google Latitude widget on my iGoogle page won't load my friends. If I expand it the friends list on the left of the screen is empty apart from the words "loading friends". The rest of the iGoogle page seems fine.

Both these things work perfectly in Safari 4, and I *think* the Latitude widget worked in Firefox 3.0.11, the last version I used before I updated. I've check with all add-ons and plug-ins removed, disabled and enabled (I hardly use any and there were no compatibility issue when I updated to 3.5). I am using a Macbook running OS X 10.5.7 and if I click "About Mozilla Firefox" it gives me the folowing: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5

Sorry for the lack of any other pertinent info that might help. I'm clueless about this sort of thing.

posted by brighton to computers & internet (5 comments total)

I have the same problem with the YouTube HTML5 demo on Windows XP.
posted by proj at 9:09 AM on July 1

I should add that I realize it's likely there are two entirely different problems here. Just hoping it might be one...
posted by brighton at 9:15 AM on July 1

The main problem with the YouTube demo is that the video is in H.264 format, which Firefox's HTML 5 video implementation doesn't support (it only supports Ogg Theora). Safari's HTML 5 video support relies on QuickTime, which does support H.264.
posted by kyten at 11:32 AM on July 1

Firefox reports a CSS parsing error on the HTML5 page as well:

Warning: Error in parsing value for 'margin-left'. Declaration dropped.
Source File: http://www.youtube.com/demo/demo.css
Line: 493
posted by caution live frogs at 12:25 PM on July 1

Kyten was right about the youtube page.

The iGoogle Latitude widget problem has been fixed by Google and is explained in the Google support forums here.
posted by brighton at 9:01 AM on August 3