W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2015

[Bug 20361] Grammar is wrong for serializers

From: <bugzilla@jessica.w3.org>
Date: Tue, 24 Mar 2015 13:55:57 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20361-3890-oXc5PHVBf5@http.www.w3.org/Bugs/Public/>

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
                 CC|                            |travil@microsoft.com

--- Comment #5 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Boris Zbarsky from comment #4)
> I still claim the entire serializer setup is overengineered.  Does anyone
> really want anything other than { attribute } for interfaces with no
> ancestors that have serializers or { inherit, attribute } for ones that have
> such ancestors?

In IE, we've only wanted (and implemented) this for the NavigationTiming [1]
and related interfaces, in order to make it easy to package and serialize the
attributes. +1 for potentially simplifying the grammar to remove use-cases
until/unless we find a good reason for them.

[1] http://www.w3.org/TR/navigation-timing/#sec-navigation-timing-interface

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 24 March 2015 13:56:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC