Bug 20008 - allow [Unforgeable] on an interface
allow [Unforgeable] on an interface
Status: RESOLVED FIXED
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL
unspecified
PC Windows 3.1
: P2 normal
: ---
Assigned To: Cameron McCormack
public-webapps-bugzilla
[v1]
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-19 23:25 UTC by Cameron McCormack
Modified: 2013-07-02 07:11 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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: http://lists.w3.org/Archives/Public/public-script-coord/2012JulSep/0144.html