This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20008 - allow [Unforgeable] on an interface
Summary: allow [Unforgeable] on an interface
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
Whiteboard: [v1]
Depends on:
Reported: 2012-11-19 23:25 UTC by Cameron McCormack
Modified: 2013-07-02 07:11 UTC (History)
2 users (show)

See Also:


Description Cameron McCormack 2012-11-19 23:25:48 UTC
Location is going to gain some members through an implements statement, like

  Location implements Blah;

but we need those imported members from Blah to be [Unforgeable] in addition to all the existing ones on Location.  So let's allow [Unforgeable] directly on interface Location, to indicate that all of its members (including the ones from the implements statement) to be unforgeable.

toString/valueOf on Location also need to be unforgeable.
Comment 1 Cameron McCormack 2012-11-19 23:38:14 UTC
See also this thread: