Closed
Bug 576652
Opened 15 years ago
Closed 14 years ago
Login button on joystiq.com does not work on Linux Seamonkey
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [SmBugEvent])
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100402 Fedora/2.0.4-1.fc13 SeaMonkey/2.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100402 Fedora/2.0.4-1.fc13 SeaMonkey/2.0.4
I'm running Seamonkey 2.0.4 on Fedora Core 13 on an x86_64 system. On this browser, I cannot log into joystiq.com. The "login" button does nothing. I have no problems with Seamonkey on other platforms. I also don't have any problems with Firefox on this machine. This is a Linux Seamonkey specific problem.
The problem occurs both on the http://www.joystiq.com/login web page and the drop-down box on the main page.
Reproducible: Always
Comment 1•15 years ago
|
||
Note:
Such errors are very unlikely a platform specific thing because Gecko is Cross platform.
I can see your reported "bug" with SM trunk Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:2.0b2pre) Gecko/20100629 SeaMonkey/2.1a3pre and also with FF3.6.6.
I used a wrong username/password ( test@example.com/1234)
After that I used IE7 and got the same issue (IE reports that there are errors on the page).
The error Console in SM and FF shows :
Error: document.getElementById("key") is null
Source File: http://www.blogsmithmedia.com/www.joystiq.com/include/login.js
Line: 69
This looks like a bug in the page unless that there are differences with a working username/password.
Comment 3•15 years ago
|
||
Which Firefox version ?
As i already wrote, i get the same problem with Firefox 3.6.6 on win32.
Comment 4•14 years ago
|
||
Looks like a website problem. Closing as INVALID. Please reopen if you can reproduce this with SeaMonkey 2.1b3 or 2.1 final.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Whiteboard: [SmBugEvent]
You need to log in
before you can comment on or make changes to this bug.
Description
•