<select> displays focus outline even if it's not focused and has no "-moz-focusring" pseudoclass

VERIFIED FIXED in Firefox 48

Status

()

defect
P4
minor
VERIFIED FIXED
3 years ago
3 years ago

People

(Reporter: arni2033, Assigned: mats)

Tracking

({testcase})

Trunk
mozilla48
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(firefox47 affected, firefox48 fixed)

Details

Attachments

(4 attachments)

Reporter

Description

3 years ago
>>>   My Info:   Win7_64, Nightly 47, 32bit, ID 20160229030448. DEFAULT THEME
STR:
1. Open attached "testcase 1"
2. Click on the free place on page, press Ctrl+Shift+R
3. Press Tab key

AR:  <select> displays focus outline even if it's not focused and has no "-moz-focusring" pseudoclass
ER:  <select> shouldn't display focus outline

Note:
 This testcase was originally made by me for bug 1214293. It's not connected to this one
Comment hidden (spam)
Comment hidden (spam)
Assignee

Updated

3 years ago
Assignee: nobody → mats
Severity: normal → minor
Keywords: testcase
Priority: -- → P4
Attachment #8727529 - Flags: review?(tnikkel) → review+
Assignee

Updated

3 years ago
Flags: in-testsuite+

Comment 7

3 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/eaa71dfff611
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
Assignee

Comment 8

3 years ago
Shouldn't this be backed out on m-c too? 
or perhaps it was but not noted by the bot for some reason?

Anyway, I'm still trying to make the reftests work, but ~12 hours to get results
from Try on Win8 doesn't help much :-(
https://treeherder.mozilla.org/#/jobs?repo=try&revision=054925a1fc85
Status: RESOLVED → REOPENED
Flags: needinfo?(mats) → needinfo?(wkocher)
Resolution: FIXED → ---
After a bit of digging, I see what happened. I backed out both patches in a single, squashed backout commit. Normally, it records all of the csets into the backout commit message, but this time it looks like it only recorded one of the csets in there, so when Tomcat used Bugherder to mark the merge, Bugherder only saw that half of the bug had been backed out, so went ahead and marked the other part as merged.

I checked the backout commit, though, and it includes the backout for both parts, so this actually was backed out fully, and it's just our tools that screwed up, not the code or either sheriff.
Flags: needinfo?(wkocher)
Target Milestone: mozilla48 → ---
Blocks: 1255877

Comment 11

3 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/009922b47d80
https://hg.mozilla.org/mozilla-central/rev/0c6911b972d1
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
Reporter

Comment 12

3 years ago
Fixed on:   Win7_64, Nightly 48, 32bit, ID 20160317030235
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.