1160749 - Clicking a toolbar button while its panel is open should hide the panel

Status: NEW

(Firefox :: Toolbars and Customization, defect, P4)

Description

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

The usual behavior of toolbar buttons and panels is that panels close when the icon is clicked again. The Hello panel doesn't follow that pattern, at least not on Windows 8 (I never noticed it on Mac, so it might be platform specific).

Comment 1

[Mark Banner (:standard8)]

Philipp, I can't reproduce this. I've tried windows 7 and 8 and I haven't been successful. Can you retry, or do you know anyone else experiencing this?

Comment 2

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

I did a little more investigation: It seems that it's actually not just the Hello panel, but also other Panels like downloads and history (not bookmarks and the hamburger menu though).

My current theory is that it's related to machines with a touch screen, because I can't reproduce it in a VM on a Mac, but it happens reliably on an XPS 13. When using touch to open and close the panels, they show the correct behavior.

Comment 3

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

I should clarify: it happens when clicking the buttons with the mouse on a device that also has a touch screen.

Comment 4

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

Interesting... it happens when I use the trackpad on my Dell XPS13, but not if I use an external mouse. Could this be another issue related to Microsofts precision trackpads?

Comment 5

[:Gijs (out for now; he/him)]

comment #2 and comment #4 make me think this shouldn't block the windows 10 tracker. Is there something I'm missing?

Comment 6

[(Currently slow to respond) Philipp Sackl [:phlsa] (Firefox UX) please use needinfo]

Hm, depends on how we interpret the win10 tracker. For me it was always »stuff we should fix to be great on Windows 10«.
But it's quite possible that this is not the most useful way to look at it :)

Comment 7

[:Gijs (out for now; he/him)]

(In reply to Philipp Sackl [:phlsa] please use needinfo from comment #6)
> Hm, depends on how we interpret the win10 tracker. For me it was always
> »stuff we should fix to be great on Windows 10«.
> But it's quite possible that this is not the most useful way to look at it :)

I tend to think of it as "things that are new issues/features for windows 10".

I think it makes sense to have a separate bug for "things we need to be great on Windows" as such, and this could go under such a metabug. We will likely need it in about a month or two anyway.