W3C home > Mailing lists > Public > www-style@w3.org > July 2014

Re: [css-syntax] Do not require digits after decimal point for number tokens

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 30 Jul 2014 16:49:29 -0500
Message-ID: <CAAWBYDBid45UFU3wqCZbr7pVbXAGuVKADboQ5XewRQax5=KOaA@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: Lea Verou <lea@verou.me>, www-style list <www-style@w3.org>
On Wed, Jul 30, 2014 at 12:52 PM, Alan Stearns <stearns@adobe.com> wrote:
> On 7/29/14, 12:42 PM, "Lea Verou" <lea@verou.me> wrote:
>>On Jul 29, 2014, at 22:20, Lea Verou <lea@verou.me> wrote:
>>> When the author is editing non integer lengths (e.g. from 2.5px to
>>>2.9px), it usually goes like this (| denotes the caret):
>>> 2.5px|
>>> 2.5|px
>>> 2.|px
>>> 2.9|px
>>> Instead of being able to observe the result of their changes, all they
>>>see is a flash, since the 3rd step makes the value invalid, then it
>>>jumps back to 2.9px. It sounds trivial, but it’s encountered so
>>>frequently that it’s incredibly annoying.
>>Actually, I just realized my example doesn't demonstrate what I meant.
>>The numbers should have been 2px to 2.1px:
> It seems to me that this should be a fix in the tools that allow
> live-editing of values. I think it would be bad to allow 2.px as a value
> in a stylesheet. Just 2. by itself might be OK, but that’s not going far
> enough to solve your use case.

Why would 2.px be bad?

Received on Wednesday, 30 July 2014 21:50:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:23 UTC