Clicking outside a chrome menu doesn't "click through" to whatever's below |
||||||||
Issue descriptionThis came up in an unrelated UX review. When a Chrome menu is opened, for example the triple-dot menu on the browser window, and a user clicks on a link outside the menu, that link should be activated and the menu should close. Instead, the menu closes but the link is not activated.
,
Oct 22
Perhaps the best thing here is to make sure they are consistent, like as a P3. e.g. the site-info page will allow click-through, while the 3-dot menu does not (on cros). Let's track this as a polish bug at low priority. Over to rob to see how it prioritizes.
,
Oct 23
,
Oct 25
,
Oct 26
This behavior actually is different across platforms with respect to whether or not the click proceeds or is canceled. Windows tends to let the click proceed. Mac cancels. If CrOS has a position on whether or not the click should proceed, then that might be worth a bug, but it's also worth having the conversion which behavior is more desirable based off of the common-case use case of a particular platform.
,
Oct 29
Chrome OS has traditionally let clicks pass through. E.g. put two windows side by side and with one window focused click on a link in the other. We don't eat it to focus but also pass the click to the site. We should be applying the same to context menues to be consistent.
,
Nov 8
,
Dec 11
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by omrilio@chromium.org
, Sep 7Owner: markchang@chromium.org