Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken events on parent DOM elements in Chromium 79.0.3945.117 #11224

Closed
theusersimons opened this issue Mar 20, 2020 · 1 comment
Closed

Broken events on parent DOM elements in Chromium 79.0.3945.117 #11224

theusersimons opened this issue Mar 20, 2020 · 1 comment

Comments

@theusersimons
Copy link

@theusersimons theusersimons commented Mar 20, 2020

Version

2.6.11

Reproduction link

https://jsfiddle.net/theusersimons/k9smeL2o/16/

Steps to reproduce

This can 't be reproduced just in the browser. We are developing an interface in a project that uses the chromium 79.0.3945.117 source code to create an in-game browser.

What is expected?

Events on the parent DOM element and on child elements are expected to work normally.

What is actually happening?

CEF stops correctly calculating the target DOM element that events are set to. For example if a click hangs on the parent element during this problem it does not extend to the entire element and the click only occurs on the final child element of the DOM.


This problem is observed with absolutely all events in the context of parent and child interaction. This problem started after version 2.5.22 of Vue. On all subsequent versions this problem exists, previously and including version 2.5.22 everything works fine.

@posva

This comment has been minimized.

Copy link
Member

@posva posva commented Mar 20, 2020

Please check https://github.com/vuejs/vue/releases/tag/v2.6.0 Important Internal Changes section, specifically the nextTick one and the linked document in Details

BTW, please be more specific when reporting a bug about what steps one must do to reproduce the problem (eg move the cursor over the element, then move it out) and the same goes with what is expected, 2 logs, 1 log, etc

@posva posva closed this Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.