- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Oct 2013 16:29:18 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23534
Bug ID: 23534
Summary: freeze/seal/preventExtensions should throw for Nodes
(and maybe any WebIDL interface)
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebIDL
Assignee: cam@mcc.id.au
Reporter: bobbyholley@gmail.com
QA Contact: public-webapps-bugzilla@w3.org
CC: annevk@annevk.nl, bzbarsky@mit.edu, mike@w3.org,
public-script-coord@w3.org
Freezing an object or calling preventExtensions theoretically means that the
prototype is fixed. But there are cases in the DOM when we need to modify the
prototype. In particular, this is the case for Nodes when adopted into the
scope of a different global (see bug 20567).
jst and I think that we should just throw when trying to do any of these
objects on any kind of WebIDL-defined object. Anne generally agrees, but there
are some considerations about self-hosted DOMs to be considered.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 16 October 2013 16:29:20 UTC