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

Re: Proposal: will-animate property

From: Ali Juma <ajuma@chromium.org>
Date: Wed, 4 Dec 2013 17:23:28 -0500
Message-ID: <CANLC6v3KY3y41KT67NmQZF+DZqsS9c1n8d12C_ky41OZS-hAMg@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: Benoit Girard <bgirard@mozilla.com>, www-style <www-style@w3.org>, "L. David Baron" <dbaron@dbaron.org>, Matt Woodrow <matt@mozilla.com>, Cameron McCormack <cmccormack@mozilla.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
On Wed, Dec 4, 2013 at 5:15 PM, Robert O'Callahan <robert@ocallahan.org>wrote:

> On Thu, Dec 5, 2013 at 11:12 AM, Benoit Girard <bgirard@mozilla.com>wrote:
>>  The problem with that approach is that when some browser adds
>>> new-property and extends will-animate syntax to support new-property, and
>>> an author writes "will-animate: transform, new-property", other browsers
>>> get no will-animate at all.
>> Can we simply require all identifiers (except all, inherit, initial,
>> unset) to be parsed?
> Yes, we proposed that. I'm talking about the problem with Ali's approach.

Could we just require the entire list to be parsed, and require
implementations to ignore any string outside of the specified set? Then
when a new-property is added to the spec, older browsers and browsers that
don't care about new-property can treat "will-animate: new-property,
transform" as just "will-animate: transform".
Received on Wednesday, 4 December 2013 22:23:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:37 UTC