498062 - Once in FaceBook, pixel location hides page info and bottom notifications are not seen

Status: RESOLVED FIXED

(Web Compatibility :: Desktop, defect)

Description

[Edward Bucaro]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.21) Gecko/20090403 SeaMonkey/1.1.16
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.21) Gecko/20090403 SeaMonkey/1.1.16

Unable to view top or bottom of FaceBook. Top is covered by header so Home, Profile and other tabs are not seen. On the bottom, the notification icon is hidden.

Reproducible: Always

Steps to Reproduce:
1. login to www.facebook.com
2. look at the page, upper tabs are hidden underneath the header column
3. the notification icon is hidden behind the footer
Actual Results:  
I've captured the screen and can provide the image. This is my first time using SeaMonkey, but I've been a long time user of Mozilla and Firefox.

Expected Results:  
Same results

Allow the pixel location to view the header and footer of facebook page

Comment 1

[Edward Bucaro]

Attachment: Screen capture of pixel location issue on facebook

Comment 2

[Serge Gautherie (:sgautherie)]

Can you reproduce with SeaMonkey v2.0a3 / current v2.0b1pre?

Comment 3

[David]

Various features in facebook do not work in Seamonkey 1.1.17, but they do in Firefox 3.0.8, such as the header view described here, and the chat feature.

Comment 4

[Mike Cordeiro]

This is the same issue I was having. Try going to about:config and searching for general.useragent.extra.seamonkey and changing it to Firefox/2.0. Facebook is browser sniffing and sending the wrong HTML to seamonkey.

Comment 5

[David]

Yes Mike that works.

Comment 6

[Chris Lawson (gone)]

Is there a chance they're doing something specific to SeaMonkey? I don't see this in Camino with the "like Firefox" portion of Camino's UA string removed, for instance.

Comment 7

[Chris Lawson (gone)]

Can someone please try this with a current SeaMonkey trunk nightly? I can't tell whether this is:

* a Gecko 1.8 problem, or 
* a combination of funky sniffing + Gecko 1.8, or 
* purely funky sniffing

If the same problem exists in a SeaMonkey trunk nightly, it's probably bad sniffing. If the problem disappears, it's probably Gecko 1.8 (although someone should spoof Sm trunk as 1.1.x to verify this).

Comment 8

[Ilya Sherman]

After a bit more investigation, this seems to be a problem with user-agent detection mixed with Gecko 1.8.  The page renders correctly with Gecko 1.9 & the SeaMonkey user-agent, but chat is still disabled.

Comment 9

[Chris Lawson (gone)]

Facebook seems to have updated their UA detection recently. Is this still a problem for anyone who was originally seeing it?

Comment 10

[David]

Seems OK now thanks

Comment 11

[Karl Dubost💡 :karlcow]

According to Comment #10