Closed
Bug 1487048
Opened 6 years ago
Closed 6 years ago
Tab key is not focusing in correct order in about:preferences#privacy
Categories
(Firefox :: Protections UI, defect, P3)
Tracking
()
VERIFIED
FIXED
Firefox 63
Tracking | Status | |
---|---|---|
firefox63 | --- | verified |
People
(Reporter: david.olah, Assigned: ehsan.akhgari)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
[Affected versions]
63.0a1 (2018-08-28)
[Affected platforms]
Windows 10, Windows 7, Ubuntu 16.04, Mac OS x
[Steps to reproduce]
1. Open Firefox and in the Hamburger Menu, click on Content Blocking
2. about:preferences#privacy will be opened and Content Blocking section will be focused
7. Navigate using the Tab key
[Expected result]
The elements are focused in order from top to bottom
[Actual result]
Drop-down from "Trackers" is focused after "Change Block List..." link.
Comment 1•6 years ago
|
||
Please note that the first "Learn More" hyper-link (above the ON-OFF button) is skipped and will not get focused using the TAB key.
Updated•6 years ago
|
Summary: [Fastblock] Tab key is not focusing in correct order in about:preferences#privacy → Tab key is not focusing in correct order in about:preferences#privacy
Comment 2•6 years ago
|
||
After the update with the new UI in about:preferences#privacy, the text string beside the newly added check-boxes are not focused neither the secondary checkboxes which are not checked. Please check the attached video for the actual state.
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Priority: -- → P3
Assignee | ||
Comment 4•6 years ago
|
||
Assignee | ||
Comment 5•6 years ago
|
||
I think the tab order issue is gone now, and the focus ring issue is all that's left.
Assignee | ||
Comment 6•6 years ago
|
||
Attachment #9005480 -
Flags: review?(mconley)
Comment 7•6 years ago
|
||
Comment on attachment 9005480 [details] [diff] [review]
Fix the focus highlights in the Content Blocking section of Preferences
For consistency with other about:preferences controls, the focusring should be around the label rather than the checkbox. Drawing it around the checkbox would be an acceptable stop-gap solution, but I believe Johann already pointed out how to properly fix this in bug 1487453 comment 1.
Attachment #9005480 -
Flags: review?(mconley) → review-
Assignee | ||
Comment 8•6 years ago
|
||
(In reply to Dão Gottwald [::dao] from comment #7)
> Comment on attachment 9005480 [details] [diff] [review]
> Fix the focus highlights in the Content Blocking section of Preferences
>
> For consistency with other about:preferences controls, the focusring should
> be around the label rather than the checkbox. Drawing it around the checkbox
> would be an acceptable stop-gap solution, but I believe Johann already
> pointed out how to properly fix this in bug 1487453 comment 1.
Can you please expand on how that would work? If I understand correctly, the src attribute would allow changing the image of the checkbox. There is a label attribute as well. But here there is another icon between the checkbox and the label, which is the reason why I was using a separate <label> element...
Flags: needinfo?(dao+bmo)
Assignee | ||
Comment 10•6 years ago
|
||
Note to self: Bryan also asked me to line up the indented rows with the icons, not the checkbox labels.
Assignee | ||
Comment 11•6 years ago
|
||
Assignee | ||
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Comment on attachment 9005790 [details]
Bug 1487048 - Use a <xul:checkbox> control to draw the icon and label of the checkboxes in the Content Blocking section; r=johannh,flod
Francesco Lodolo [:flod] has approved the revision.
Attachment #9005790 -
Flags: review+
Comment 14•6 years ago
|
||
Comment on attachment 9005790 [details]
Bug 1487048 - Use a <xul:checkbox> control to draw the icon and label of the checkboxes in the Content Blocking section; r=johannh,flod
Johann Hofmann [:johannh] has approved the revision.
Attachment #9005790 -
Flags: review+
Comment 15•6 years ago
|
||
Pushed by eakhgari@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/45710448c230
Use a <xul:checkbox> control to draw the icon and label of the checkboxes in the Content Blocking section; r=johannh,flod
Comment 17•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
Updated•6 years ago
|
Assignee: nobody → ehsan
Updated•6 years ago
|
Flags: qe-verify+
Reporter | ||
Comment 19•6 years ago
|
||
Comment 1 and Comment 2 is still reproducible. Should I create other Bug for these and close this as Verified or will be fixed in this particular one?
Flags: needinfo?(ehsan)
Assignee | ||
Comment 20•6 years ago
|
||
Please feel free, since I can't reproduce them.
Flags: needinfo?(ehsan)
Reporter | ||
Comment 21•6 years ago
|
||
I can reproduce both on Nightly 64.0a1 (2018-09-10), Windows 10 and Ubuntu 16.04.
As you can see in the attachment, "learn more" below the Exceptions... is skipped, also the unselected radio buttons are skipped.
Assignee | ||
Comment 22•6 years ago
|
||
(In reply to David Olah from comment #21)
> Created attachment 9008064 [details]
> bandicam 2018-09-11 17-41-55-671.mp4
>
> I can reproduce both on Nightly 64.0a1 (2018-09-10), Windows 10 and Ubuntu
> 16.04.
> As you can see in the attachment, "learn more" below the Exceptions... is
> skipped, also the unselected radio buttons are skipped.
I see...
So here:
* The first "learn more" link is actually before Exceptions in tab order not after, that's why it appears to be skipped in your video recording. But if you started tabbing from the search box, you would see very different results. So no real bug there IMO.
* The other issues you've pointed out around unselected radio buttons being skipped are all to be expected. This is how radio buttons work in native applications in both Windows and Linux, and we imitate that behavior in Firefox. No real but there either IMO.
If you disagree, you should feel free to open new bugs.
Reporter | ||
Comment 23•6 years ago
|
||
I verified the issue described in Comment 0 and it is no longer reproducible. Also, based on Comment 22, I am marking the issue as verified.
You need to log in
before you can comment on or make changes to this bug.
Description
•