- From: Rune Lillesveen <rune@opera.com>
- Date: Thu, 01 Nov 2012 11:45:58 +0100
- To: "CSS WG" <www-style@w3.org>
- Cc: "Kenneth Rohde Christiansen" <kenneth.christiansen@gmail.com>
On Mon, 29 Oct 2012 16:24:27 +0100, Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com> wrote: > Sure that is an option I've updated the ED to say that viewport units are relative to the initial viewport. > On Mon, Oct 29, 2012 at 4:17 PM, Rune Lillesveen <rune@opera.com> wrote: >> On Mon, 29 Oct 2012 00:53:20 +0100, Christiansen, Kenneth R >> <kenneth.r.christiansen@intel.com> wrote: >> >> I think it would make sense to disallow these within the @viewport rule. >> >> >> Or resolve the values against the initial viewport. "width: 2vw" would >> be >> the same as "width: 200%". >> >> >> >> Kenneth >> >> >> >> From: fremycompany_pub@yahoo.com [mailto:fremycompany_pub@yahoo.com] >> Sent: Sunday, October 28, 2012 6:34 AM >> To: CSS WG; Christiansen, Kenneth R; Øyvind Stenhaug >> Subject: RE: [css-device-adapt] Units >> >> >> >> While we are at it, I’ve discovered an issue with CSS-Device-Adapt : >> there’s >> nothing preventing you to specify the @viewport { width } declaration in >> viewport units (vh,vw,vmin,vmax). >> >> >> >> However, those units are ill-defined in the @viewport rule since the >> width >> isn’t properly computed at this time. >> >> >> >> @viewport { width: 2vw; } >> >> >> >> In the only browser supporting both @viewport and Viewport Units >> (IE10), the >> declaration is causing weird rounding issues for viewport units later >> in the >> document so this clearly has border-effects proving it’s not completely >> ignored (even if the browser didn’t enter in a loop incrementing the >> viewport width at each relayout operation). >> >> >> >> To make things simpler, I propose to invalidate the use of Viewport >> Units in >> the Viewport AtRule. -- Rune Lillesveen
Received on Thursday, 1 November 2012 10:46:18 UTC