Closed Bug 318437 Opened 20 years ago Closed 16 years ago

Some buttons no longer function after Deer Park alpha 2 update

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: danswer, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051024 Firefox/1.6a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051024 Firefox/1.6a1 After a Firefox (Deer Park alpha 2) automatic update today, certain buttons on certain sites no longer function. Specifically, I am no longer able to use the Search button at http://ebay.com nor am I able to retrieve email at http://z6.com (specifically, I am not able to submit my login information using the Login button). I am able to log in at yahoo and hotmail, and I am able to search using google. And if you are reading this, I'm also able to use the submit button on bugzilla Reproducible: Always Steps to Reproduce: Go to http://www.ebay.com (or http://z6.com or http://z6.mail.everyone.net/email/scripts/loginuser.pl) and after filling out something to search for, press the Search button (or the Login button). The page does not appear to be submitted (ie. these sites are no longer functional). However, links work. The problem does not happen with IE 6. This started happening after the automatic update about 12 hours ago.
My comment about being able to search on http://google.com was incomplete. It is true that I am able to search using http://google.com However, searching on google results in a window where the search results are below and there is a section where you can search again at the top. I cannot search again having performed a search. In other words, the Search button that appears as the result of a search does not work. However, I am able to click the links, such as Group, and the resultant Search button there is usable. The reason why I thought to mention this is that this seems to be the scenario with the fewest amount of errors in the javascript console. In particular, it seems that the problem possibly has something to do with cursor not being able to be read in the CSS.
This problem has not resurfaced so I am closing out this report.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.