517777 - facebook publisher post box glitch

Status: RESOLVED DUPLICATE of bug 516842

(Tech Evangelism Graveyard :: Other, defect)

Description

[Scooter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

Seamonkey is not allowing the publisher post function on facebook to work, the cursor defaults into page text. Comment post boxes work, but not new posts. Doing this on 3 different computers running latest SM build. FB works fine on same machines using Firefox or that wannabe MS browser.

Reproducible: Always

Steps to Reproduce:
1.login to Facebook and attempt to enter a status post.
2.
3.
Actual Results:  
when a character is typed into the post box, the cursor appears in the pre-existing page text and highlights the first instance of the character that was typed and an error chime sounds.

Expected Results:  
text entry into post box

Comment 1

[Robert Kaiser]

This is not a SeaMonkey bug, the recent Facebook problem are a problem on their side, they are checking for "Firefox" in the browser identification and discriminating against unknown browsers.

Comment 2

[Chris Lawson (gone)]

kairo: did you confirm that by testing this with Seamonkey, and again with Seamonkey spoofing as Firefox?

Comment 4

[Robert Kaiser]

(In reply to comment #1)
> This is not a SeaMonkey bug, the recent Facebook problem are a problem on their
> side, they are checking for "Firefox" in the browser identification and
> discriminating against unknown browsers.

No, but we get repeated reports in the newsgroups about those problems recently (since 1 or two weeks or so) and all those people can resolve it be adding a "Firefox/3.5" or so the their UA.

Comment 5

[Chris Lawson (gone)]

(In reply to comment #4)
> (In reply to comment #1)
> > This is not a SeaMonkey bug, the recent Facebook problem are a problem on their
> > side, they are checking for "Firefox" in the browser identification and
> > discriminating against unknown browsers.
> 
> No

Would you, please? If you do, feel free to confirm this.

Comment 6

[Robert Kaiser]

I can't, I don't have a FB account and don't want to visit that crap of a service at all.