- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jan 2025 23:19:19 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[cssom-view] Allow elementFromPoint and elementsFromPoint to traverse shadow roots`, and agreed to the following: * `RESOLVED: add shadowRoots param to ePFP() to match caretPFP()` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> kbabbitt: request is to have elementFromPoint() be able to traverse shadows, so you can get the "real" element when it's in a shadow<br> <TabAtkins> astearns: simialr to caretPositionFromPoint(), i see<br> <emilio> q+<br> <TabAtkins> proposed: add shadowRoots param to ePFP() to match caretPFP()<br> <ydaniv> +1<br> <astearns> ack emilio<br> <TabAtkins> emilio: somewhat related, Gecko has a way of getting raw nodes from point<br> <TabAtkins> emilio: text nodes, etc<br> <TabAtkins> emilio: it always felt kinda funny that elementFromPoint() wouldn't giv eyou that.<br> <TabAtkins> emilio: wonder if that owuld be useful<br> <TabAtkins> emilio: nodesFromPoint(), returning the actual node when the point is text, rather than closest element<br> <TabAtkins> astearns: seems useful to me, open an issue?<br> <TabAtkins> emilio: we also have the ability to ask what elements/nodes intersect a rect, needed for finger tap testing<br> <TabAtkins> emilio: I'll file an issue<br> <TabAtkins> RESOLVED: add shadowRoots param to ePFP() to match caretPFP()<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10992#issuecomment-2623143244 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 January 2025 23:19:20 UTC