- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 16:41:12 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[CSS-UI] caret-shape: block/underscore and overflow`, and agreed to the following: * `RESOLVED: when caret is past the end of the line, attempt to show it even if it overflows. Browser may clip it or reposition it` <details><summary>The full IRC log of that discussion</summary> <kbabbitt> florian: the resolution might be just fine but I think we considered a too narrow question<br> <kbabbitt> ... would like to make sure we still agree when we consider whole question<br> <kbabbitt> ... this was raised in the context of block and underscore caret<br> <kbabbitt> ... but we need to consider spec for any caret<br> <kbabbitt> ... question was what to do when the caret overflows but we're assuming in our discussion that the text doesn't<br> <kbabbitt> ... so we wondered what happens if only caret overflows<br> <kbabbitt> ... but this is not necessarily true, text itself might overflow as well<br> <kbabbitt> ... so we said that when the caret is past the end of the line we should show it anyway even if it overflows<br> <kbabbitt> ... and there may be some intermediate<br> <kbabbitt> ... but if you think of text which overflows line and caret at end of text<br> <kbabbitt> ... and whole thing is happening in box with scroll or hidden overflow<br> <kbabbitt> ... position of caret is outside the box somewhere after the text you can't see<br> <kbabbitt> ... not just about clipping at this point, may also be about positioning<br> <kbabbitt> ... for example in firefox, if you have text that's longer than line, overflowing andh idden<br> <kbabbitt> ... and caret at end of that<br> <kbabbitt> ... caret is shown at visible end of line, not where text ends<br> <kbabbitt> ... and other browsers, in that situation, caret isn't shown at all<br> <kbabbitt> ... not showing it at all is a kind of clipping, and we might say we want to clip<br> <kbabbitt> ... but firefox does more than clipping, it repositions caret to where you can see it<br> <Rossen9> q?<br> <kbabbitt> ... I think the general idea is you should show caret, you might need to clip, is reasonable, but you might need to do more than clip and reposition to make it visible<br> <kbabbitt> ... I suspect we want to keep this ? for now at least, though if we want to insist you have to show it, I don't mind<br> <schenney> q+<br> <kbabbitt> ... I think we should not ban firefox behavior at least<br> <Rossen9> ack schenney<br> <kbabbitt> schenney: support the view of not banning it<br> <kbabbitt> ... from my perspective firefox's ui gives some sign that editing is happening<br> <kbabbitt> ... that's a choice, chrome chooses not to, that's a choice<br> <kbabbitt> ... agree this should be open to browser interpretation<br> <kbabbitt> Rossen9: I like the approach of starting with a "may" and requiring more strictly later<br> <kbabbitt> ... for interop<br> <kbabbitt> florian: Proposal: when caret is past the end of the line, attempt to show it even if it overflows. Browser may clip it or reposition it<br> <kbabbitt> Rossen9: additional feedback or objections?<br> <kbabbitt> RESOLVED: when caret is past the end of the line, attempt to show it even if it overflows. Browser may clip it or reposition 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/10289#issuecomment-3079413337 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 July 2025 16:41:13 UTC