Closed Bug 1393059 Opened 7 years ago Closed 6 years ago

Location bar shouldn't change/lose selection if the window loses and regains focus, even if browser.urlbar.clickSelectsAll is true

Categories

(Firefox :: Address Bar, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 --- wontfix

People

(Reporter: Atoll, Unassigned)

Details

(Keywords: parity-chrome, parity-safari)

When I'm trying to build a search in the smart bar, I sometimes refer to other apps for my search terms, and switch to them (using Command-Tab on OS X) to look at them. Unfortunately, every time I do this, Firefox throws out my cursor position in the smartbar and re-selects the entire typed content to date. At least three times out of five, I forgot to re-locate the cursor and wiped out my entire query. Please don't do this.
Nightly, fresh profile no addons etc.
(Parity: This problem does not occur in Chrome+Safari)
Component: General → Location Bar
Summary: Smart bar cursor position is discarded when I alt-tab away from Firefox for less than a second → Location bar shouldn't change/lose selection if the window loses and regains focus, even if browser.urlbar.clickSelectsAll is true
Whiteboard: [parity-Safari][parity-Chrome]
I see similar behavior on Linux, regardless of the value of browser.urlbar.clickSelectsAll, but only when switching tabs within Firefox (which is bad enough). I'm not reproducing when switching focus to and from another app.
On OS X today, I am no longer able to reproduce the problem using Cmd-Tab to another application; cursor selection and/or position is maintained correctly. However, I am able to reproduce comment 3's "switching tabs" effect; when I either put the cursor at the end of the field or select some text, and then switch tabs, all text is deselected and the cursor moves to the beginning of the field.
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Whiteboard: [parity-Safari][parity-Chrome]

Given the original issue is fixed, as per comment 4, I'm going to close this as WFM.

Comment 3 is already covered by bug 1429020 and similar bugs.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.