Re: [csswg-drafts] [css-text] Should browsers apply a minimum width to tabs?

The CSS Working Group just discussed `Applying a min width to rendered tabs`.

<details><summary>The full IRC log of that discussion</summary>
&lt;gregwhitworth> Topic: Applying a min width to rendered tabs<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/2883#issuecomment-421733978<br>
&lt;gregwhitworth> florian: when you have tab stops, if you have a tab - you're supposed to go forward in the line<br>
&lt;gregwhitworth> florian: if your text is coming extremely close to the next tab stop, should there be a minimum size?<br>
&lt;gregwhitworth> florian: Chrome, it jumps to the next one at a specific size and it seems reasonable in a monospaced font<br>
&lt;fantasai> s/Resolved:/RESOLVED:/g<br>
&lt;gregwhitworth> florian: I was thinking about going with 1 space, but maybe we should go smaller than a space<br>
&lt;gregwhitworth> florian: in a proportional font, spaces are already really small - 0.5ch<br>
&lt;gregwhitworth> florian: I'm wanting to take this normative as makes sense<br>
&lt;emilio> astearns: Any comments from the non-chrome team?<br>
&lt;fantasai> +1 from me anyway<br>
&lt;emilio> astearns: proposal is minimum spacing is 0.5ch<br>
&lt;emilio> astearns: objections?<br>
&lt;emilio> astearns: RESOLVED: Make the normative change<br>
&lt;emilio> myles: Should link to the primary font concept<br>
&lt;fantasai> https://www.w3.org/TR/css-values-3/#ch<br>
&lt;emilio> fantasai: it already does via the ch value, though it's not actually the primary font<br>
&lt;emilio> fantasai: it's ch, it's not ambiguous<br>
&lt;emilio> emilio: is it what Blink implements?<br>
&lt;emilio> myles: if the code is the same as WK it's not exactly the same, but we can say ch on the spec<br>
&lt;emilio> astearns: the test for this is not going to test this exactly<br>
&lt;emilio> fantasai: why not?<br>
&lt;emilio> astearns: flaky tests / pixel differences<br>
&lt;emilio> fantasai: fine<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2883#issuecomment-422872689 using your GitHub account

Received on Wednesday, 19 September 2018 16:39:44 UTC