Closed
Bug 855603
Opened 11 years ago
Closed 5 years ago
"Show/Hide new tab page" button has a selection border (focus ring)
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: nealp9084, Unassigned)
References
Details
(Keywords: polish)
Attachments
(1 file)
10.38 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:22.0) Gecko/20130325 Firefox/22.0 Build ID: 20130325170119 Steps to reproduce: 1. Open a new tab 2. Click on the "Show/Hide the new tab page" button, which is located on the top right of the page 3. Move the cursor away from the button but don't click anywhere else Actual results: The button has a selection border around it Expected results: The button should not have a selection border. You wouldn't put one on the reload or tab group button; this button is no exception.
Comment 1•11 years ago
|
||
> You wouldn't put one on the reload or tab group button; this button is no exception.
Maybe that's an accessibility bug of Tab Groups. On the other hand, it may be enough if the button gets a focus ring when selected using keyboard (in which case it's GOOD that there is a ring).
Comment 2•10 years ago
|
||
Mass-move to Firefox::New Tab Page. Filter on new-tab-page-component.
Component: Tabbed Browser → New Tab Page
Comment 3•10 years ago
|
||
Hello ,I am new to bug fixing and i would like to take up this bug.Can someone kindly help me with what should be done?
Comment 4•10 years ago
|
||
Dão, is this a valid issue? Reading bug 418521 and using moz-focusring on about:newtab this doesn't sound broken to me but I have no idea what our behavior should be.
Flags: needinfo?(dao)
Comment 6•5 years ago
|
||
Hello!
This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience.
Please help us triage by reopening if this issue still persists and should be addressed.
Thanks!
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•