Am 10.08.2012 12:06 schrieb Odin Hørthe Omdal:
On Thu, 09 Aug 2012 18:54:10 +0200, Kornel Lesiński
<kor...@geekhood.net> wrote:
One stylesheet can be easily reused for pixel-perfect 1x/2x layout,
but pixel-perfect 1.5x requires its own sizes incompatible with 1x/2x.
Apart from it possibly being a self-fulfilling prophecy – isn't this
too much premature “optimization” ?
I think we can safely assume that authors will always want to prepare
as few assets and stylesheets as they can, and will prefer integer
units to fractional ones (1px line vs 1.3333px line).
I don't see the big problem, I think the spec is fine here. Yes it
allows for putting a float there, but authors won't use it, so what's
the problem? The spec already say you should use the number to calculate
the correct intrinsic size, and the implementation will know what to do
with a float number there if someone finds an actual use for it.
This isn't limiting it for the sake of making anything easier, it's not
like "the x is an integer" is any easier than "the x is a float". And if
you *do* somehow find a good use for it down the line (and I believe
there might be, maybe 0.5x) it'll be there and work. No harm. :)
One hypothetic use case for 0.5x could be: Future UAs may want to
progressively load sources in order to display a lowres image very
quickly, and increase quality if there is enough bandwidth to do so,
similarly to what we know from interlaced GIFs. Authors then might want
to provide 0.5x and even 0.25x sources for this purpose.
