- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 22 Apr 2026 16:30:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-gaps-1] `overlap-join` with `between` rule visibility``, and agreed to the following: * `RESOLVED: go with new approach about whether there is a junction to handle or not` * `RESOLVED: option A for naming, use 'junction' and 'cap'` <details><summary>The full IRC log of that discussion</summary> <JoshT> javierct: [shares screen]<br> <JoshT> ... we have resolved on overlap-join to join decorations<br> <JoshT> ... then in f2f, we talked about what happens with unjoined ones. do we want to extend them across empty cells?<br> <JoshT> ... how exactly we're not sure, so we want to resolve on them today<br> <JoshT> ... we want to only join segments that we want to join<br> <JoshT> ... suggestion was: currently we have edge and interior points. instead, we could do 'does this point have a crossing decoration - something to join with - or not?'<br> <JoshT> ... we think this is the way forward<br> <JoshT> ... so 'does this end point meet an intersection or not?'<br> <JoshT> ... edge endpoints still don't have anything to join, so the author could still set a different behaviour<br> <JoshT> ... we might want to control them separately, still<br> <JoshT> ... question is 'edge' and 'interior' names don't make sense any more. Kevin asked on social media. 'cap' and 'junction' or 'open' and 'close'<br> <JoshT> s/close/closed/<br> <JoshT> ... our current behaviour is still preserved, but we can deal with the cases discussed in the f2f<br> <JoshT> astearns: suggestion is to choose between these two names?<br> <JoshT> javierct: we resolved on trimming the ones with no intersection to join with<br> <JoshT> ... proposal for that is this behaviour to move from edge/interior to some other distinction<br> <JoshT> ... we want to know if that's the correct way to solve this problem. and then work out the names<br> <JoshT> astearns: so for first part, do we continue with previous edge/interior distinction, or go with 'is there a junction or not'? options?<br> <JoshT> ... it makes sense to me. I'm concerned if people will say 'I want to treat the non existent junctions at the edge separately to interior ones'<br> <JoshT> javierct: that's something we considered. we don't have use cases to treat them differently<br> <JoshT> astearns: i would be happy to change it to the proposal<br> <JoshT> ... no other opinions. shall we resolve?<br> <JoshT> RESOLVED: go with new approach about whether there is a junction to handle or not<br> <JoshT> astearns: any opinions on name options? or additional options?<br> <bramus> junction seems fine<br> <JoshT> ... i prefer junction rather than open or closed is that it seems more direct<br> <hoch> +1 for junction<br> <JoshT> q+<br> <emeyer> +1 to junction (if we’re not going to use intersection)<br> <bramus> scribe+<br> <SebastianZ> For what it's worth, I agree with astearns.<br> <bkardell> junction seems pretty good<br> <astearns> ack JoshT<br> <bramus> JoshT: fan of junction, not sure what cap means<br> <davidjmarland> same<br> <bramus> javierct: look at diagrams here. cap is somewhat abstract I guess … would not know what it means in terms of english … like top or cap<br> <emeyer> +1<br> <astearns> ack ChrisL<br> <Zakim> ChrisL, you wanted to check this is for selectors-5, right?<br> <emeyer> q+<br> <bramus> … it is a bit abstract. the cap/junction was the most voted one in the bsky thread by kbabbitt<br> <bramus> … people were leaning towards it<br> <hoch> q+<br> <bramus> … one could make similar args about open/closed<br> <bramus> … could look at it as ?? but agree with astearns that junction makes more sense<br> <bramus> JoshT: definitely agree with junction<br> <bramus> … in British English we might call cap a “dead end” more or “cul de sac”<br> <davidjmarland> short?<br> <PaulG> terminator?<br> <bkardell> oooh terminator<br> <emeyer> q-<br> <astearns> ack hoch<br> <rachelandrew> I thought terminator as well<br> <bramus> hoch: part of the origin of cap was from the CSS Propertye for svgs: stroke-line-cap<br> <emeyer> I was going to make the same point about SVG terminology.<br> <bramus> … so there is precedent fo rindicating this dangling line<br> <hoch> q-<br> <bramus> JoshT: makes sense<br> <bramus> +1<br> <JohnJansen> I thought "end cap" which I have on the end of my garden hose to prevent leaking...<br> <JoshT> astearns: shall we resolve on option A for now and leave it open for later bikeshedding?<br> <JoshT> PROPOSED: option A for naming, use 'junction' and 'cap'<br> <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/22-css-minutes.html fantasai<br> <bkardell> I like terminator<br> <JoshT> RESOLVED: option A for naming, use 'junction' and 'cap'<br> <JoshT> astearns: in the write up, I think it should be called in option A put 'start' and 'end' values at the end of all of the longhands<br> <bramus> +1<br> <SebastianZ> +1<br> <davidjmarland> +1<br> <jBreiland> +1<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13697#issuecomment-4298033174 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 April 2026 16:30:05 UTC