Closed Bug 1694285 Opened 3 years ago Closed 3 years ago

Proton: Ensure it's clear where arrow panels that open automatically are anchored to

Categories

(Toolkit :: Themes, defect, P1)

defect

Tracking

()

RESOLVED FIXED
89 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox86 --- unaffected
firefox87 --- disabled
firefox88 --- disabled
firefox89 --- fixed

People

(Reporter: dao, Assigned: mconley)

References

(Blocks 1 open bug, Regressed 1 open bug, Regression)

Details

(Keywords: regression, Whiteboard: [proton-door-hangers])

Attachments

(1 file)

I haven't checked this in practice, but just by reading bug 1693710's patch it seems that there's going to be a problem for arrow panels that open automatically but can be dismissed for later interaction. E.g. the Update Nightly notification is anchored to the main menu button but there are several buttons next to it it could just as well be anchored to.

To a lesser extent this might also be a problem / look unclear for popups that cannot be dismissed such as the add-on installation doorhanger.

Set release status flags based on info from the regressing bug 1693710

Priority: -- → P2

The spec calls for the anchor to have a background colour applied when the panel is open. We get some of that already with panels that are anchored to buttons, like the AppMenu button, downloads, protections, identity and control center panel. We don't get it for panels that anchor when those buttons are not activated.

The various permission panel icons, for example, should have this background colour applied. Same with the AppMenu panel when something anchors to it, despite the fact that the AppMenu might itself not be open.

The background colour should match the secondary button hover colour.

Hey Neil, how hard do you think it'd be to set an anchoring attribute on the anchor node for a panel when the panel is opened, and remove it when the panel goes away? Is that straight-forward enough to do in the panel.js binding in popupshowing and removing in popuphiding on anchorNode, or are there edge-cases that panel.js wouldn't be able to easily handle?

Flags: needinfo?(enndeakin)

For a <panel> that should be ok. You probably want popupshown/popuphidden instead though.

Flags: needinfo?(enndeakin)
Priority: P2 → P1

This seems to take care of the cases that I'm aware of:

  • DOM Permission panels
  • Panels that anchor to the AppMenu button, like update notification messages, or
    add-on install confirmation messages.
Assignee: nobody → mconley
Status: NEW → ASSIGNED
Attachment #9211849 - Attachment description: Bug 1694285 - Make it more obvious where panels are anchored to with Proton enabled. r?Gijs! → Bug 1694285 - Make it more obvious where panels are anchored to with Proton enabled. r?Gijs!,dao!
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6308384f47a7
Make it more obvious where panels are anchored to with Proton enabled. r=Gijs,desktop-theme-reviewers,dao
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch
Depends on: 1701664
Regressions: 1701664
Regressions: 1702125
Regressions: 1703624
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: