这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@NavidZ
Copy link

@NavidZ NavidZ commented May 13, 2019

Chrome 73 starts sending click even to the common
ancestor of down and up events even when one was
inside the input element and the other one was
outside. This caused this library to fail in the
following scenario:
User presses down on the picker input which causes
the date picker and overlay to be shown. When user
releases the button the overlay gets the up event
and the common ancestor of these elements will get
the click. Since there is a click handler on the
document to close the popup, the calendar popup immediately
closes.

Using pointercapture API to capture the rest of the
pointerevents stream to the picker input it ensures
the click event target is the picker input and that ensures
the click handler doesn't dismiss the popup.

Chrome 73 starts sending click even to the common
ancestor of down and up events even when one was
inside the input element and the other one was
outside. This caused this library to fail in the
following scenario:
User presses down on the picker input which causes
the date picker and overlay to be shown. When user
releases the button the overlay gets the up event
and the common ancestor of these elements will get
the click. Since there is a click handler on the
document to close the popup, the calendar popup immediately
closes.

Using pointercapture API to capture the rest of the
pointerevents stream to the picker input it ensures
the click event target is the picker input and that ensures
the click handler doesn't dismiss the popup.
@DanielRuf
Copy link
Contributor

Hi @NavidZ,

Please check the failing tests.

@DanielRuf
Copy link
Contributor

Also this will not work in older browsers.

We will not merge this solution for the regression bug for v3.

As others already wrote, revert the change and provide a proper migration path.

https://bugs.chromium.org/p/chromium/issues/detail?id=941910

You already confirmed that this is a regression bug in Chromium and we will not add other workarounds or solutions like this for one specific browser bug. I still not understand why the Chromium developers do not simply revert or fix this and push the responsibility to us library maintainers.

Pickadate 3.6.3 works without any problems so we do not need this vendor specific solution.

@DanielRuf DanielRuf closed this May 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants