- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2023 00:46:40 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-highlight-api] Exposing shadow DOM highlights in highlightsFromPoint()`, and agreed to the following: * `RESOLVED: Change highlights from point to work on document or shadow root with the intention of synchronizing how highlights and elements from point work. Open a new issue to harmonize the specs and doing the research` <details><summary>The full IRC log of that discussion</summary> <dael> dandclark: This is about a highlight api v2 that we raised during tpac about making highlights interactive on scenarios like spellcheck and can click the word and handle an event knowing it was highlighted<br> <dael> dandclark: One issue during tpac was exposing highlights in shadow dom. Initial formulation was on css.highlights global. Don't want the api to return highlights in shadow. Alternative is follow example of point which can be called on document or shadow root and it gives elements under the coords on the shadow<br> <dael> dandclark: That seems like a close analog so should follow. Move highlights to be on document or shadow root.<br> <dael> dandclark: one wrinkle is point doesn't seem to say it's callable on doc or shadow roots. Seems to also be slight inconsistency between blink and geck about what can be returned if it's on shadow so some details to work out<br> <dael> dandclark: Still seems to be best to pursue<br> <dael> TabAtkins: Reasonable to me<br> <dael> astearns: Do you have an opinion about when this is called on shadow root d owe return light dom?<br> <dael> dandclark: Loose opinion is I would expect only return in the shadow dom. That seems most natural, but loosely help opinion<br> <dael> astearns: Other opinions?<br> <dael> astearns: Concerns?<br> <dael> TabAtkins: For question about light dom, are you thinking about slotted light dom into the shadow or arbitary overflow.<br> <dael> astearns: Thinking arbitary but slotted is right. I would expect slotted.<br> <dael> astearns: Definitely something to look into. I think I prefer the route of changing hightlights to work on either doc or shadow root<br> <dael> dandclark: Maybe resolve today to move to document and sharow root. Reality of browsers for point should be further investigated and we should match to that and agree what makes sense for both APIs. We can develop an opinion for both<br> <dael> astearns: I think point is our document; cssom view<br> <dael> astearns: Prop: Change highlights from point to work on document or shadow root with the intention of synchronizing how highlights and elements from point work. Open a new issue to harmonize the specs and doing the research<br> <dael> dandclark: Sounds right<br> <dael> astearns: Concerns?<br> <dael> astearns: Obj?<br> <dael> GameMaker: Since I've been doing highlights, want to say this seems to line up with things that will be okay<br> <dael> RESOLVED: Change highlights from point to work on document or shadow root with the intention of synchronizing how highlights and elements from point work. Open a new issue to harmonize the specs and doing the research<br> <dael> astearns: dandclark I may ask you to make point element edits as well<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7766#issuecomment-1371600242 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 January 2023 00:46:42 UTC