Closed Bug 374881 Opened 13 years ago Closed 13 years ago
.focus() causes Up, Down, Page Up, Page Down, Home and End keys to not function on other sites .
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20070309 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20070309 Firefox/220.127.116.11 Happens with: Firefox 18.104.22.168 and 22.214.171.124 Does not happen with: Firefox 126.96.36.199 and previous version Installation: Clean Profile: New Extensions: None The problem IS definitely caused by the way Google has the cursor automatically inserted into the text box. The Google Firefox start page is default in Firefox. After starting the browser and visiting any site after, the navigation keys do not work at all. Visiting Google from your bookmarks has the same result, so it does not have to be set as the default start page to reproduce this, but it must be in the bookmarks. Reproducible: Always Steps to Reproduce: 1. Add www.google.com to your bookmarks 2. Add www.broadbandreports.com to your bookmarks (Note: The addresses must be added to bookmarks; typing in location/address bar will fail to reproduce this issue) 3. Close Firefox 4. Start Firefox 5. Click on www.google.com from your bookmarks 6. DO NOT type in the Google search box or click anywhere 7. Click on www.broadbandreports.com from your bookmarks 8. Try Up, Down, Page Up, Page Down, Home and End keys This would also be reproducible by having Google (or Firefox start page) as your default start page. Start the browser, then simply click on Broadband Reports in the bookmarks and this will also reproduce just the same. It does not have to be Broadband Reports site either, it can be ANY site that has the vertical scroll bar. Actual Results: The navigation keys mentioned above do not work on any other site. Expected Results: The navigation keys should still work. The Google text box somehow steals focus. This has always worked perfectly with Firefox 188.8.131.52 and previous versions, but has not worked since 184.108.40.206. - The Google text box somehow steals focus. Typically when focus has been taken this way, you would be able to click on the background of the web page to bring focus back and allow the navigation keys to work as per normal. However, that is not the case with this. The only work-around is to click in the text box, then click on the background or by typing something into the text box. - Another work-around in this scenario is by going to Google, then to Broadband Reports and clicking in the Username, Password or Search box at the top of their site, then clicking on the background of the site. The keys will then start working again. - This is definitely an issue caused by Google's automatic insertion of the cursor into their search text box.
Summary: Automatic cursor insertion into text box (Google search / Firefox start page) causing Up, Down, Page Up, Page Down, Home and End keys to not function on other sites. → textbox.focus() causes Up, Down, Page Up, Page Down, Home and End keys to not function on other sites.
I just wanted to reiterate the fact that this issue is "out-of-the-box" on Firefox 220.127.116.11 and 18.104.22.168 simply because the default start page is that Google Firefox page. Brand new, clean installation, new profile will reproduce this issue right from the get-go.
This is a regression between 2006-09-19 07 and 2006-09-19 11. http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2006-09-19+06%3A00&maxdate=2006-09-19+12%3A00 On branch it regressed between the nightlies of 15 and 16 Jan 2007, which seems to point to Bug 286933.
More info: This does NOT reproduce at www.hotmail.com Google and Hotmail both have the cursor automatically inserted into the text box and visually appears the same. However, this is reproducible only on Google and not with Hotmail. I would assume that they both use different methods to insert the cursor. Hopefully this last bit of information will help narrow down the specific problem.
Confirming based on Ria finding a regression range.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This fixes it, but it is really a hack. But I think this is safe for the branch. nsFormFillController::Unload doesn't seem to get called at all when a new page gets loaded. (btw, it seems to me that should happen on the pagehide event, not the unload event)
Comment on attachment 259408 [details] [diff] [review] patch? I would like to just back out the original patch for now, at least on the branch.
a=dveditz for backing out bug 286933. Please remove "fixed22.214.171.124" from that bug when you have.
Assignee: mconnor → mano
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
(In reply to comment #10) > I would like to just back out the original patch for now, at least on the > branch. Ok, but there really seems to be something fundamentally wrong with nsFormFillController::Unload not be called at all. Should I file a new bug on that?
yes, please do, and cc me (please also set some blocking flags, it seems to me like it may cause leaks and/or crashes).
I filed bug 376563.
verified fixed 126.96.36.199 using the steps to reproduce from comment #0 on Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:188.8.131.52pre) Gecko/2007042805 BonEcho/184.108.40.206pre and Up, Down, Page Up, Page Down, Home and End keys are working -> adding verified keywords.
You need to log in before you can comment on or make changes to this bug.