Re: [csswg-drafts] [css-pseudo-4] ::first-letter should include space separators (#5154)

The CSS Working Group just discussed `[css-pseudo-4] ::first-letter should include space separators`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-pseudo-4] ::first-letter should include space separators<br>
&lt;dael> github:<br>
&lt;dael> fantasai: Issue about how not including spaces but only punct.<br>
&lt;dael> fantasai: NUmber of punct related patterns with punct space letter.<br>
&lt;dael> fantasai: Prop is update as desc ^ to include intervening whitespace in ::first-letter<br>
&lt;dael> Rossen_: Feedback or objections?<br>
&lt;Rossen_> q?<br>
&lt;Rossen_> ack chris<br>
&lt;dael> faceless2_: If not followed by letter does that go with it?<br>
&lt;dael> fantasai: Currently ::first-letter is a letter or digit. If you have paragraph with only punct there is no ::first-letter<br>
&lt;dael> tantek: I accept the situation exists in prose. What I'm not seeing in issue is documentation or example like print example of ::first-letter with punct and space and letter all as first letter<br>
&lt;dael> tantek: Open to keeping issue open but needs more data to accept b/c otherwise might make worse<br>
&lt;dael> tantek: Inclusion of punct in ::first-letter at all we had numerious examples in multi lang. Since I'm not seeing that I would reject<br>
&lt;dael> fantasai: Do you have those examples?<br>
&lt;dael> tantek: Yeah, need to check my bookshelf<br>
&lt;dael> fantasai: Typical case if if " in french you have to include space. Usually not full sized.<br>
&lt;dael> tantek: My point is a french first letter with a " and a letter. Need to see that example to move forward.<br>
&lt;astearns> there are two references in the initial comment<br>
&lt;dael> myIes: I think I disagree with tantek. If we're doing ::first-letter that punch through pucnt this has to happen if we support french<br>
&lt;dael> florian: Question is valid, does french do that<br>
&lt;dael> fantasai: This raised b/c issue filed against browsers and browsers wanted spec update<br>
&lt;dael> Rossen_: And there are bugs linked in issue<br>
&lt;dael> tantek: At time we found print examples in magizines so it was not hard to find. If that's not true in french I'd push back. Someone more familiar with french I'd ask have they ever seen it in french and share an example rather then rely on theory<br>
&lt;dael> Rossen_: French only?<br>
&lt;dael> tantek: I think Norwegian is also provided in issue<br>
&lt;dael> tantek: Either is sufficent evidence.<br>
&lt;dael> tantek: When talking details I'd rather based on examples and not completionism reasoning.<br>
&lt;dael> dauwhe: We use spacing like this all the time " and than ' would be sep by a space. If that's all ::first-letter we'd want it all selected. We use spaces between punct all the time.<br>
&lt;dael> tantek: That's different than prop.<br>
&lt;dael> fantasai: That's included. All punct before first letter is included as well as any intervening space. So this would solve dauwhe use case<br>
&lt;dael> tantek: Have you seen it in print?<br>
&lt;dael> fantasai: We have it in English<br>
&lt;dael> dauwhe: I can't remember if I've seen that at start of chapter with initial-letter. Somewhere that I'd need a ::first-letter selector to capture that combo of glyphs<br>
&lt;dael> tantek: Anything adding complexity to platform has a cost. It's reasonable to request some examples produces, esp with other lang<br>
&lt;dael> astearns: True there is a cost, but this is a case w/o interop. We can spec what is requested and have engines that don't do it match those that do and we gain interop<br>
&lt;dael> Rossen_: And this is Mozilla right that would need to add to be interop<br>
&lt;dael> tantek: I couldn't determine from issue which engines did what<br>
&lt;dael> astearns: We know some do and some don't. Seems reasonable to spec this knowing there are strings that have this behavior and people like to apply ::first-letter to things. I don't know it's nec to come up with print example to spec this and have engines match<br>
&lt;dael> Rossen_: I think 2nd paragraph in opening issue comment. Safari incl spaces, Chrome doesn't. 10y/o bug from Mozilla desc this.<br>
&lt;dael> Rossen_: Safari is ahead and Moz and Blink need to catch up<br>
&lt;dael> Rossen_: There is precent for interop<br>
&lt;dael> plinss: If there isn't inerop there is fail in testing or unclarity in spec. Need to fix either way<br>
&lt;dael> tantek: I'd worry about compat if there's a 10 y/o bug<br>
&lt;dael> fantasai: Safari shipped with this. Not sure why worried about compat<br>
&lt;dael> tantek: Safari might have compat problem<br>
&lt;dael> fantasai: Doubt it<br>
&lt;dael> florian: Esp since people filing bugs against Chrome and FF<br>
&lt;dael> fantasai: We've spent a long time on this. I'd rather we not spend more time. tantek will you block and want us to go look for more b/c the lack of interop and old bugs is not enough?<br>
&lt;Rossen_> q?<br>
&lt;dael> tantek: Prefer to request examples and leave open<br>
&lt;dael> florian: We're trying to align so I don't object<br>
&lt;dael> Rossen_: Sounds like tantek you object on resolving based on lack of evidence.<br>
&lt;dael> Rossen_: Let's record that objection. It will go into the issue.<br>
&lt;dael> Rossen_: I'm hoping dauwhe or Richard can get an example and we can resolve next week.<br>
&lt;dael> Rossen_: Either way we'll come back to discuss this around interop.<br>
&lt;florian> s/We're trying to align so I don't object/I would agree with tantek if there had been interop and we were proposing to change, but there isn't interop and we're trying to align, so I don't agree/<br>
&lt;tantek> That's fine, didn't intend so much time on this issue<br>
&lt;dael> Rossen_: tantek do you agree with this?<br>
&lt;dael> tantek: Yes, reasonable. Thank you<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 15 July 2020 16:32:23 UTC