Closed Bug 1187007 Opened 9 years ago Closed 9 years ago

Display name field keeps focus outline even after pressing cancel

Categories

(Firefox :: Sync, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
Firefox 43
Tracking Status
firefox43 --- verified

People

(Reporter: rfeeley, Assigned: eoger)

Details

Attachments

(3 files, 1 obsolete file)

Attached image sync-focus.png
      No description provided.
Attached patch bug-1187007.patch (obsolete) — Splinter Review
Attachment #8638693 - Flags: review?(markh)
Comment on attachment 8638693 [details] [diff] [review]
bug-1187007.patch

Review of attachment 8638693 [details] [diff] [review]:
-----------------------------------------------------------------

Strange that I don't see the problem on Windows. Wouldn't it be better to just .focus() the "change" button?
Attachment #8638693 - Flags: review?(markh)
Attached image focus on button.gif
I tried to focus the button and unfortunately on mac osx it feels really weird.
Flags: needinfo?(markh)
We discussed on IRC that the .blur() (with a comment why it is necessary - it shouldn't be) and a .focus() of the change button (so an element close to the previously focused element gets final focus) is ok.
Flags: needinfo?(markh)
hrm - now I'm not so sure :/ On my mac:

Try these str:
* Open prefs - device textbox has no border/highlight/focusring/whatever-it-is
* Click "change" - gets the ring.
* Click "cancel" - keeps the ring (ie, the point of this bug)
* Press Tab a few times.

Note how focus shifts to other elements, but that ring remains - so the issue doesn't seem to be focus but "something else" - we should find what that is.
(well - focus related, but if there is a blur event going missing it seems worth digging into a little)
The |disabled| property setter doesn't seem to blur its attached element when set to true, maybe we should fill a bug for this?
(In reply to Edouard Oger [:eoger] from comment #7)
> The |disabled| property setter doesn't seem to blur its attached element
> when set to true, maybe we should fill a bug for this?

I think the element is losing focus (as focus moves to other elements) - so I suspect something like the blur event isn't delivered to disabled elements rather than auto-bluring it on being disabled.
Filed XUL bug 1194032
Sorry if there's been some confusion, but can you please put up a tweaked patch with what comment 4 says (assuming it works) and with a comment referencing that older focus-related bug, with r=me and checkin-needed etc.
Flags: needinfo?(edouard.oger)
Attachment #8638693 - Attachment is obsolete: true
Flags: needinfo?(edouard.oger)
Attachment #8652459 - Flags: review+
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/498b7d4817e1
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 43
I have reproduced this bug on Firefox nightly Version 42.0a1

It's fixed and verified on Latest Developer Edition
Build ID 	20151017004025
User Agent 	Mozilla/5.0 (Windows NT 6.3; rv:43.0) Gecko/20100101 Firefox/43.0

Tested OS- Windows8.1 32bit
QA Whiteboard: [testday-20151016]
Thanks!
Marking as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: