- From: <bugzilla@jessica.w3.org>
- Date: Tue, 24 Mar 2015 13:55:57 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20361
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