- From: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>
- Date: Wed, 14 Nov 2012 17:29:13 +0100
- To: Rune Lillesveen <rune@opera.com>
- Cc: www-style@w3.org
Received on Wednesday, 14 November 2012 16:30:12 UTC
That is a good point. We should look into doing the same after we have our initial CSS device adaptation implementation in trunk. Cheers Kenneth On Wed, Nov 14, 2012 at 3:42 PM, Rune Lillesveen <rune@opera.com> wrote: > ** > On Wed, 14 Nov 2012 15:29:09 +0100, Kenneth Rohde Christiansen < > kenneth.christiansen@gmail.com> wrote: > > Why do we have to map it to the @viewport syntax? I believe for WebKit we > will just have a separate code path for the meta element, which ensures > that it keeps the same algorithm as always. > > > What do you do when there's both an @viewport and a <meta> element present? > > Mapping <meta> to @viewport will at give you a well-defined behavior > through cascading. You could of course say that one must ignore the <meta> > elements in the presence of one or more @viewport rules. > > -- > Rune Lillesveen > > -- Kenneth Rohde Christiansen Senior Engineer, WebKit, Qt, EFL Phone +45 4093 0598 / E-mail kenneth at webkit. <http://gmail.com>org ﹆﹆﹆
Received on Wednesday, 14 November 2012 16:30:12 UTC