W3C home > Mailing lists > Public > www-style@w3.org > October 2013

Re: [css-device-adapt] Apply @viewport to top-level documents only

From: Sylvain Galineau <galineau@adobe.com>
Date: Thu, 3 Oct 2013 17:34:57 -0700
To: "L. David Baron" <dbaron@dbaron.org>, Fran├žois REMY <francois.remy.dev@outlook.com>
CC: Rune Lillesveen <rune@opera.com>, www-style list <www-style@w3.org>, Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>
Message-ID: <CE735A43.DB9F%galineau@adobe.com>

On 10/3/13 4:26 PM, "L. David Baron" <dbaron@dbaron.org> wrote:
>On Thursday 2013-10-03 06:20 -0700, Sylvain Galineau wrote:
>> On 10/3/13 5:56 AM, "Kenneth Rohde Christiansen"
>><kenneth.christiansen@gmail.com> wrote:
>> >I think it is fine to push that to a level 2.
>> That was my first inclination but this is a constraint, not an
>> feature. It's a lot easier to loosen a constrain in a future level than
>> the reverse.
>I'm having trouble telling whether Sylvain is agreeing or
>disagreeing here, but either way I'd like to point out that relaxing
>constraints can cause compatibility problems.  It's certainly less
>risky than functional changes, but for features that have been
>around a long time, the Web tends to end up with pages using
>features in a way that doesn't do anything.  These are sometimes the
>result of author attempts that didn't work, but weren't removed from
>the page.  So making those things suddenly do something can break

Fair; after all, the document in that iframe may have its own viewport
rule that never did anything. But this is an issue only if we change the
scope for existing markup; we could allow viewport rules to apply in
subframes provided the author defines some new additional descriptor.

Received on Friday, 4 October 2013 00:35:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:02 UTC