PointerEvents seem to break some default handler assumptions in Blink |
||||
Issue descriptionSome event handlers in Blink have mouse-specific assumptions which can break with PointerEvents. For example, MediaControlVolumeSliderElement::defaultEventHandler and MediaControlTimelineElement::defaultEventHandler returns early for mouseover/out/move events, and pointerover/out/move events cause problems (e.g. Issue 677900 ). We should check all default handlers (media, forms, ...) to make sure there is no unexpected event handling somewhere.
,
Jan 19 2017
Found another case: shadow dom event path ( Issue 680377 ). These seem to be next possible suspects: HTMLSelectElement::menuListDefaultEventHandler HTMLTextAreaElement::defaultEventHandler MediaControls::defaultEventHandler TextFieldInputType::forwardEvent
,
Jul 13 2017
Could this be related to the range and number inputs not working? For some reason they break when I switch from my drawing tablet to my mouse and back. Afterwards I can control them with my mouse but not with my tablet.
,
Jul 13 2017
Hi daan93@: this could be related but not sure. Do you have a link to a (minimal) repro?
,
Jul 13
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 13
mustaq@ can this be closed now? It appears that we have resolved all the issues that have come up so far. So maybe a meta bug is not needed anymore? I'm closing this for now. Feel free to open if you believe it needs to remain open to track anything.
,
Jul 13
LGTM, thanks. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Jan 10 2017