Closed
Bug 1301754
Opened 9 years ago
Closed 1 year ago
Trying to define an accessor property on a DOM proxy with a named setter should fail
Categories
(Core :: DOM: Bindings (WebIDL), defect, P3)
Core
DOM: Bindings (WebIDL)
Tracking
()
RESOLVED
DUPLICATE
of bug 1853542
| Tracking | Status | |
|---|---|---|
| firefox51 | --- | affected |
People
(Reporter: bzbarsky, Unassigned)
References
Details
See http://heycam.github.io/webidl/#defineownproperty steps 1.1 and 2.2.2.1.
We don't do that now. Testcase that should throw:
var x = document.documentElement.dataset;
Object.defineProperty(x, "nosuchpropanywhere", {get: function() {} });
|
Reporter | |
Comment 1•9 years ago
|
||
Equivalent Chrome issue at https://bugs.chromium.org/p/chromium/issues/detail?id=645542
|
||
Updated•9 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 3•7 years ago
|
||
Chrome is having issues doing this for named setters because of Node crud. I am going to spin off the indexed setter into bug 1479793 and we can sort this one out separately.
Component: DOM → DOM: Bindings (WebIDL)
Summary: Trying to define an accessor property on a DOM proxy with a named/indexed setter should fail → Trying to define an accessor property on a DOM proxy with a named setter should fail
|
|
Reporter | |
Updated•5 years ago
|
Mentor: bzbarsky
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•