New issue
Advanced search Search tips

Issue 711201 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
Fixing-touch


Sign in to add a comment

Sometimes tapping the hamburger menu icon doesn't open the menu

Project Member Reported by dhadd...@chromium.org, Apr 13 2017

Issue description

Kevin / 9455.0.0 / 59.0.3068.1

Open MD Settings
Click the hamburger menu icon

Occasionally it will just get selected when you tap/click it. 
 
Labels: -Proj-MaterialDesign-CrOS Proj-MaterialDesign-WebUI

Comment 2 by dbeam@chromium.org, Apr 13 2017

this is just how touch works, if you do long touch or just a really light touch it might not be a normal 'tap' afaik
Owner: dschuyler@chromium.org
Status: Assigned (was: Untriaged)
Any time I tapped/clicked the button, the sidenav opened. However, I found that if I clicked in the regions above/below the hamburger button it would highlight the button without triggering the sidenav.

See https://screenshot.googleplex.com/xPa5KK5BCQ0

@dschuyler is this something you can look into or pass to someone who can?
Summary: Sometimes tapping the hamburger menu icon doesn't open the menu (was: Sometimes tapping/clicking the hamburger menu icon doesn't open the menu)
Sorry, to clarify my last comment I could only repro this with touch/stylus, not mouse.
Labels: Hotlist-MD-Settings-Structure
Status: Available (was: Assigned)
I'm marking this Available so that someone with a touch screen or stylus can look into it (see #4).

It seems like (don't know for sure) the touch/stylus is triggering on a margin click (rather than just content+padding). 

The margins occupy the areas that tbuckley@ marks in #3. This may be fixable by simply removing the margin on the paper-icon-button. I can set "margin: 0;" on it and that doesn't seem to affect the page layout. I'm tempted to patch that in just to see if it fixes it, but it would be better if someone could fix and try it.
Owner: ----
Cc: -dbeam@chromium.org
Labels: -M-59
Owner: steve...@chromium.org
Status: Assigned (was: Available)
@stevenjb would you be able to check this on a touchscreen device?
Cc: steve...@chromium.org
Components: UI>Input>Touch
Owner: ----
Status: Untriaged (was: Assigned)
I can get this to happen. I can also get it to happen less frequently with other events. I can not reliably reproduce it though and can not tell what the pattern is.

It definitely seems to be a lower level issue with how touch events are determined.

Labels: -Pri-2 Pri-3
Owner: steve...@chromium.org
Status: Assigned (was: Untriaged)
Steven, this is a low priority bug. I can repro reliably. I know you looked t it before, but can you help triage this?
I can investigate. I suspect this is not specific to settings but that the event is not always correctly being sent, but I will confirm that.

Status: Archived (was: Assigned)

Sign in to add a comment