- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Feb 2019 22:58:55 +0000
- To: public-css-archive@w3.org
> > Unclear whether or not the form feed causes breaks to be removed. > > Shouldn't be, rendering as a different character doesn't change its identity.... Okay. > > Why doesn't the spec say they're removed instead of rendered as U+200B? > > Because you didn't want to in [#855 (comment)](https://github.com/w3c/csswg-drafts/issues/855#issuecomment-380435969) ? :) heehee. Yes, I see now. I'll see if I can come up with an example where it matters. > If we removed the ZWSP along with the white space, we'd lose important behavior that it represents, like a line break opportunity / break in joining. I'm not sure that preserving it is doing authors any favors. Is this implemented anywhere, and do we know of authors who have used this mechanism to un-break lines? I'd like to hear what their expectations / desires are. > it's the table of contents for the core standard. Can't we do better somehow? 😕 > Adjusted the wording. 👍 > OK, I'll add an example. :) 👍 > so I think it's better to leave them outside of a note. 🤷🏻♂️ Okay. > https://www.w3.org/TR/css-text-3/#character-properties Ah, I see. It's pretty unfortunate we have to have special cases for Unicode. Presumably other text engines don't have these special cases, which means other editors should have the special cases, or CSS should adopt whatever behavior the other editors have. Therefore, either: 1. These special cases should be moved into Unicode, allowing the behavior to be shared among all text editors, or 2. We should find a new way of solving this problem -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3461#issuecomment-460838086 using your GitHub account
Received on Tuesday, 5 February 2019 22:58:57 UTC