- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Jun 2017 05:11:29 +0000
- To: public-css-archive@w3.org
@SebastianZ [commented](https://github.com/w3c/csswg-drafts/issues/1518#issuecomment-310872706) in #1518: > I'd say the behavior should be aligned first, so it's easier to add the new values. and this issue is about one non-interoperable behavior we could align before we discuss adding a new behavior (if WG agreed to add a new behavior.) Your proposed syntax has `inline-start` and `inline-end`: ```css letter-spacing: normal | <length> [ inline-start || inline-end ]? ``` but what impls do today are (from my testing, maybe inaccurate): * Blink and Gecko add spacing to the end-side of bidi resolved direction. This is different from `inline-end`, like when `<span dir=rtl>english</span>`, `inline-end` is left but "the end-side of bidi resolved direction" is right. * Edge and WebKit add spacing to the [line-right]. Given @aharon-lanin's comment above: > IMHO, letter-spacing is pretty much unusable in Gecko and Blink when applied to a mixture of LTR and RTL characters. I think Blink can try to change to Edge/WebKit behavior to see if people complaints. This change doesn't affect the width of line, just which side spacing appears, and the current behavior is said "unusable", so I think this is a safe change. Would you be willing to align Gecko to Edge/WebKit on this regard? If yes, we can make this interoperable and explainable using keywrods like `line-right`. If Gecko doesn't agree, hmm, that's hard. We probably need to seek for a behavior where 4 impls can agree to align to. [line-right]: https://drafts.csswg.org/css-writing-modes-3/#line-right -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1517#issuecomment-310965212 using your GitHub account
Received on Monday, 26 June 2017 05:11:36 UTC