Modal dialog on tab-close does not clearly indicate active-inactive button states
Categories
(Core :: Widget: Cocoa, defect, P3)
Tracking
()
People
(Reporter: Atoll, Unassigned)
Details
Attachments
(3 files)
On macOS latest and Nightly 2019-03-11, the attached modal dialog thrown by Firefox when I tried to close a tab contains two buttons.
Which button will activate when I press return — the brighter one, or the shadow-ier one?
Using a shade of gray for the primary button, that is only slightly differentiated from the non-default buttons, violates various HID guidelines, including Firefox's (Photon) and Apple's (macOS):
Behaviours — Primary — Behaviour styles such as hover, pressed and focus of a primary button:
Default Background: Blue 60 #0060df
— https://design.firefox.com/photon/components/buttons.html
A default push button is prominent in appearance and automatically performs its action when the user presses Return.
— https://developer.apple.com/design/human-interface-guidelines/macos/buttons/push-buttons/
Updated•7 years ago
|
Comment 1•7 years ago
|
||
This looks a UI design/front-end issue, which is not "user events and focus handling" problem.
I have no idea which module fits well, but guess should be one under Firefox product.
Comment 2•7 years ago
|
||
I've tested this issue on several machines Windows 10, Mac OS X and Ubuntu 16.04. On Ubuntu & Mac OS X the issue can be reproduced as presented in the description.
- In windows 10, on Firefox versions the modal dialog triggered has a different appearance, it can be observed that the "Leave Page" button has blue borders - due the fact that the previous option (invoking the leaving from that page). I guess this is a properly aspects of this modal dialog to appear.
- In Ubuntu this modal looks more confusing, both buttons have the same appearance even at hover-over action. I will attach screenshots to see the differences.
- In Mac OS X on all Firefox versions the modal dialog appears as in the screenshot posted by @:Atoll
@Hsin-Yi Tsai I will set a component to this issue and if isn't an appropriate one please feel free to change it.
Since this issue affects multiple platforms and is not tagged macOS specifically, could someone from Firefox team please help me ensure this bug gets cloned/moved/etc. appropriately to help Ubuntu users as well?
Updated•7 years ago
|
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Updated•4 years ago
|
Updated•3 years ago
|
Description
•