Closed
Bug 784073
Opened 13 years ago
Closed 12 years ago
Metro Firefox brings up new tab page when focusing location bar with autocomplete
Categories
(Firefox for Metro Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bbondy, Assigned: mbrubeck)
References
Details
(Whiteboard: [completed-elm])
Attachments
(1 file)
Steps to reproduce:
1. Open metro Firefox.
2. Start typing something in, autocomplete pops up
3. Press Ctrl+L, new tab page pops up
Expected results:
autcomplete should remain
Actual results:
New tab page pops up
Assignee | ||
Comment 2•12 years ago
|
||
This issue is caused by this code, added by bug 747786. Blurring the urlbar causes it to exit "filtering" mode. It's not clear what bug this is supposed to work around or how to reproduce it. Are there details anywhere?
If we can't remove this blur, then we'll need to add more code to work around it and restore the filtering...
Attachment #660618 -
Flags: feedback?(jmathies)
Attachment #660618 -
Flags: feedback?(hello)
![]() |
||
Comment 3•12 years ago
|
||
I think that's been in there since the initial copy from mobile. I tried searching back through blame but couldn't find anything. I'd say if it's breaking something, take it out and see what happens.
Assignee | ||
Comment 4•12 years ago
|
||
This code was never in mobile. It was added to browser/metro by this changeset:
https://hg.mozilla.org/projects/elm/rev/ea88e925d52f#l12.118
![]() |
||
Comment 5•12 years ago
|
||
Comment on attachment 660618 [details] [diff] [review]
patch
I commented this out and did a little testing, I see no side effects.
Attachment #660618 -
Flags: feedback?(jmathies) → feedback+
Comment 6•12 years ago
|
||
Comment on attachment 660618 [details] [diff] [review]
patch
Sorry for being slow to notice this request.
+1 for removing the `mode` variable.
As for the .blurFocusedElement() bit, that was part of me trying to clobber an issue where the URL bar would visually be selected, but the keyboard wouldn't show up and allow you to type text in (due to a11y binding issues). That was related to some buggy initial changes that I did to the autocomplete XBL binding several months ago, which because the autocomplete XBL is an nsIAccessibleProvider, broke some of the relevant a11y bindings.
Some of my later refactoring work on autocomplete fixed all of those issues as far as I'm aware, so +1 removing the .blurFocusedElement() call, too.
Attachment #660618 -
Flags: feedback?(hello) → feedback+
Assignee | ||
Comment 7•12 years ago
|
||
Comment on attachment 660618 [details] [diff] [review]
patch
Based on jwilde's comment, I think we should land this.
Attachment #660618 -
Flags: review?(jmathies)
![]() |
||
Comment 8•12 years ago
|
||
Comment on attachment 660618 [details] [diff] [review]
patch
I've been running with this in my queue - no issues. r+
Attachment #660618 -
Flags: review?(jmathies) → review+
![]() |
||
Updated•12 years ago
|
Product: Firefox → Firefox for Metro
Assignee | ||
Comment 9•12 years ago
|
||
Landed on elm a while ago:
http://hg.mozilla.org/projects/elm/rev/72cf22864861
Whiteboard: [completed-elm]
Assignee | ||
Comment 10•12 years ago
|
||
Resolving bugs in the Firefox for Metro product that are fixed on the elm branch. Sorry for the bugspam. Search your email for "bugspam-elm" if you want to find and delete all of these messages at once.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•