W3C home > Mailing lists > Public > www-style@w3.org > June 2008

Re: [css3-mediaqueries] Query on numeric component of resolution

From: Stewart Brodie <stewart.brodie@antplc.com>
Date: Wed, 18 Jun 2008 13:22:04 +0100
To: fantasai <fantasai.lists@inkedblade.net>
Cc: Anne van Kesteren <annevk@opera.com>, www-style@w3.org, "L. David Baron" <dbaron@dbaron.org>
Message-ID: <3626d583bd45e74137439bf5963c1cc19f32a239@localhost>

fantasai <fantasai.lists@inkedblade.net> wrote:

> Anne van Kesteren wrote:
> > 
> > On Tue, 10 Jun 2008 13:47:08 +0200, Anne van Kesteren <annevk@opera.com>

> > wrote:
> >> On Mon, 09 Jun 2008 22:28:59 +0200, fantasai 
> >> <fantasai.lists@inkedblade.net> wrote:
> >>> Depends on how you want error handling to work. I assume you want 
> >>> 100dpi to be valid and 100.5dpi to be invalid. What about 100.0dpi? 
> >>> I'd try to get
> >>> David Baron's opinion on that one.
> >>
> >> Opera supports floats as values. We can change that to integers if 
> >> that's more desirable. (Changing to integers would mean that 100.0dpi 
> >> becomes invalid obviously.)
> > 
> > I defined <resolution> in the editor's draft to be an <integer> 
> > immediately followed by a unit identifier. I hope that's acceptable to 
> > everyone.
> 
> Based on Christoph's comments, I think you should allow non-integer
> numbers.

It doesn't really matter, as long as I have a definition of what is
acceptable syntax for parsing and what constitutes valid/invalid, because
then I can implement it.


-- 
Stewart Brodie
Software Engineer
ANT Software Limited
Received on Wednesday, 18 June 2008 12:22:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:07 GMT