Issues in Firefox and Safari when combined with core-menu-button

googlearchive / core-splitter

A split bar and dragging on it will resize the sibling element

10 stars 12 forks source link

Issues in Firefox and Safari when combined with core-menu-button #17

Closed jakemac53 closed 9 years ago

jakemac53 commented 9 years ago

If you have a core-splitter and a core-menu-button then after opening and closing the menu the splitter stops behaving properly.

Pure JS repro: http://jsbin.com/mexiwafuje/1/edit?html,output

Original report https://groups.google.com/a/dartlang.org/forum/?utm_medium=email&utm_source=footer#!msg/web/ahHE8RWi8yA/vM_NfmoiLGsJ

frankiefu commented 9 years ago

Seems like an issue in polymer-gestures. When I close the popup menu, the events (mousedown, mousemove and mouseup) are also getting removed from the body. Those events on the body are necessary for track to work properly.

dfreedm commented 9 years ago

Also broken in Chrome when ShadowDOM Polyfill is forced.

dfreedm commented 9 years ago

Found it. core-overlay adds and removes some capturing event handlers on document. The gesture recognizers treat event listener removals on document specially for mouse and PointerEvents for touch-like event handling.

Comparisons with the bare document reference fail in ShadowDOM.