- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2022 16:18:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-highlight-api] Incubating custom highlight pointer event handling in CSSWG`, and agreed to the following: * `RESOLVED: Incubate this in CSSWG` * `RESOLVED: Create a highlight L2 spec, dandclark is an editor` <details><summary>The full IRC log of that discussion</summary> <emilio> topic: [css-highlight-api] Incubating custom highlight pointer event handling in CSSWG<br> <emilio> github: https://github.com/w3c/csswg-drafts/issues/7447<br> <emilio> dandclark: Highlight API had some progress these last couple years<br> <emilio> ... but no progress to be able to interact w/ highlights<br> <emilio> ... common use case is spellcheck<br> <emilio> ... there's no way to interact with highlighted ranges<br> <emilio> ... so a super useful addition would be to add pointer events to highlighted ranges<br> <florian> q+<br> <emilio> ... there's various ways to determine how they'd be routed etc<br> <emilio> ... but I wanted to check whether this is the right place for this, since this is a bit more DOM-y<br> <emilio> ... some first steps would be moving some issues from the MSEdgeExplainers repo to CSSWG<br> <emilio> ... we can do some spec PRs and prototyping<br> <astearns> ack florian<br> <emilio> florian: I think the use cases are numerous and compelling, and proposed API looks pretty good at first sight<br> <emilio> ... there are a number of interesting questions: things like dealing with overlapping ranges, and how to dispatch to the DOM in general<br> <TabAtkins> Agree the use-cases for the feature are good and worth developing. Fine with this group taking on the work; we do DOM-ish stuff sometimes, and it feels reasonable to handle this in the same group as the rest of the CSS feature.<br> <emilio> florian: the other similar thing that comes up is other pseudo-elements<br> <emilio> ... is this a missed opportunity to fix that too?<br> <emilio> ... anyways I think the best thing to do is bringing it in-group<br> <emilio> astearns: is csswg the only place you have considered bringing in?<br> <emilio> q+<br> <emilio> dandclark: for now csswg, but we possibly also want to raise a tag review and other groups like whatwg<br> <fantasai> emilio: My first question is whether, there's a Selection and Editing API WG, which already has a buch of interop problems to solve<br> <fantasai> emilio: Other question is, do we really need to dispatch new events on these, or can we re-use the existing machinery?<br> <fantasai> emilio: [missed]<br> <fantasai> emilio: I don't know whether StaticRange has it as well<br> <fantasai> emilio: there are ways to check interaction of pointer events<br> <fantasai> emilio: It seems to me there's some other areas where this could benefit from, other groups that could also help here<br> <fantasai> emilio: especially editingWG<br> <fantasai> emilio: lots of interaction with ShadowDOM and stuff<br> <emilio> s/missed/add a convenient way to check whether an event intersects with a highlight<br> <fantasai> dandclark: [missed]<br> <fantasai> dandclark: But would think it's good to start here in CSSWG<br> <fantasai> astearns: Emilio, any objection to starting here?<br> <fantasai> emilio: no objection<br> <fantasai> astearns: Any other comments<br> <fantasai> astearns: I suggest we take this as an incubation in the CSSWG, noting that it's merely an incubation<br> <emilio> astearns: objections?<br> <emilio> RESOLVED: Incubate this in CSSWG<br> <emilio> dandclark: there's a section in the existing draft about this, which is just a missing section<br> <emilio> ... do we want to put it there?<br> <emilio> astearns: seems like a reasonable place to start?<br> <emilio> fantasai: do we want to put it into a L2 spec instead? Seems like highlight API is relatively stable<br> <emilio> florian: was about to suggest the same<br> <chris> A level 2 diff spec seems a better way, agreed<br> <emilio> dandclark: that works for me, might have some follow-up questions about process<br> <hober> present-<br> <emilio> astearns: who's the current editor?<br> <emilio> florian: I'm one of them<br> <GameMaker> I'm the third editor<br> <emilio> fantasai: there's 5 open issues on L1, we should consider trying to fix them and move to CR<br> <emilio> astearns: dandclark, would you want to be an editor of L2?<br> <emilio> dandclark: sure<br> <emilio> RESOLVED: Create a highlight L2 spec, dandclark is an editor<br> <TabAtkins> ol' D&D Clark, as I always read it<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7447#issuecomment-1183422904 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 July 2022 16:18:29 UTC