Re: [css3-text] should 'tab-size' be in spaces or '0' characters?

As an author, I believe that tab size in spaces is an expected behavior
for authors. One can always change it using the ‘ch’ unit, so what
the point in removing a possibility of defining tab size in spaces?

Sites can use non-monospaced fonts in sort of CMS for example for
some reason (such as readability or similarity with output), but user
may want to copy some code which have tabs from other source and align
something with it using spaces since it's hard to use tabs in textareas–
it conflicts with navigating fields.


L. David Baron <dbaron@dbaron.org> писал(а) в своём письме Mon, 25 Mar  
2013 08:58:26 +0400:

> http://dev.w3.org/csswg/css3-text/#tab-size defines a 'tab-size'
> property taking an integer to be multiplied by the advance width of
> the space (U+0020) character.
>
> However, http://dev.w3.org/csswg/css3-values/#font-relative-lengths
> defines the 'ch' unit as using the advance width of the '0' (U+0030)
> character, which I believe was the result of implementation
> experience that '0' produced good results for sizing in proportional
> fonts, and made no difference in monospace fonts.  (I think that
> implementation experience related specifically to sizing of text
> inputs.)
>
> Should 'tab-size' instead use the '0' width rather than the ' '
> width?  I think I would prefer such a change.

Received on Monday, 25 March 2013 20:26:12 UTC