Closed Bug 1301754 Opened 8 years ago Closed 15 days ago

Trying to define an accessor property on a DOM proxy with a named setter should fail

Categories

(Core :: DOM: Bindings (WebIDL), defect, P3)

Product:
Core
Component:
DOM: Bindings (WebIDL)
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1853542
Tracking Flags:
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() {} });
Priority: -- → P3
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
Mentor: bzbarsky
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 15 days ago
Duplicate of bug: 1853542
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.