"Show/Hide new tab page" button has a selection border (focus ring)

NEW
Unassigned

Status

()

--
trivial
6 years ago
4 years ago

People

(Reporter: nealp9084, Unassigned)

Tracking

({polish})

Trunk
x86_64
Linux
polish
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 730547 [details]
Selection_001.png

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.
(Reporter)

Updated

6 years ago
Severity: normal → trivial

Comment 1

5 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).
Blocks: 455553
Status: UNCONFIRMED → NEW
Component: Untriaged → Tabbed Browser
Ever confirmed: true
Keywords: polish
Summary: "Show/Hide new tab page" button has a selection border → "Show/Hide new tab page" button has a selection border (focus ring)
Mass-move to Firefox::New Tab Page.

Filter on new-tab-page-component.
Component: Tabbed Browser → New Tab Page

Comment 3

4 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?
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)
(dashboard cleanup)
Flags: needinfo?(dao)
You need to log in before you can comment on or make changes to this bug.