-
Notifications
You must be signed in to change notification settings - Fork 378
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
It is unclear how elementFromPoint and elementsFromPoint should work #736
Comments
FYI. There is an issue filed for csswg: w3c/csswg-drafts#556 |
I think it's fine to continue discussion there, but as long as we keep this repository around we should list this in a tracking issue somewhere, so a search for elementFromPoint in open issues here gives you a link. |
Maybe we should discuss closing down this repository in favor of exclusively using whatwg/dom / whatwg/html / w3c/csswg-drafts / w3c/uievents for where the various bits ended up. |
I think that's a great idea @annevk. Having these discussions in whatwg/dom and whatwg/html would bring visibility to people who don't follow this repository. It also eliminates the confusions of what should be filed here. |
FYI. The previous attempt to close this repository is here: #652. |
I strongly oppose closing this repository and its issue tracker. |
The spec says
"these methods and attributes are defined in the similar way as currently defined in Document, considering only the current node tree. "
But what does that mean? What is 'current node tree'? Does it mean the tree rooted to Document, including shadow DOMs, or are the methods supposed to return only nodes inside ShadowRoot in case ShadowDOM.element(s)FromPoint is called?
See also #735
The text was updated successfully, but these errors were encountered: