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 24043 - [Custom]: Need to check writable too.
Summary: [Custom]: Need to check writable too.
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency tree / graph
 
Reported: 2013-12-09 23:55 UTC by Erik Arvidsson
Modified: 2014-05-08 22:02 UTC (History)
3 users (show)

See Also:

Attachments

Description Erik Arvidsson 2013-12-09 23:55:01 UTC 
"PROTOTYPE has a non-configurable property named constructor, throw a NotSupportedError and stop."

If it is non-configurable but writable it is fine for us to change the value of the property.
Comment 1 Dominic Cooney 2013-12-10 00:57:34 UTC 
The reason we check configurable and not just writable is so that we can produce prototype whose constructor property is configured the same way Web IDL specifies an Interface Prototype Object's constructor property is configured.

This is just for alignment with Web IDL. From the Chrome implementation perspective, I think it would be technically feasible to relax this requirement.

This could be done in Level 2 of the spec, since it would turn errors into non-errors.
Comment 2 Dimitri Glazkov 2014-05-08 21:53:21 UTC 
I think the spec should stay aligned with Web IDL, right? Please reopen if you feel otherwise.
Comment 3 Erik Arvidsson 2014-05-08 22:02:35 UTC 
Fair enough.