24043 2013-12-09 23:55:01 +0000 [Custom]: Need to check writable too. 2014-05-08 22:02:35 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified All All RESOLVED WONTFIX P2 normal --- 14968 1 erik.arvidsson dglazkov dominicc mike public-webapps public-webapps-bugzilla oldest_to_newest 97361 0 erik.arvidsson 2013-12-09 23:55:01 +0000 "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. 97363 1 dominicc 2013-12-10 00:57:34 +0000 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. 105492 2 dglazkov 2014-05-08 21:53:21 +0000 I think the spec should stay aligned with Web IDL, right? Please reopen if you feel otherwise. 105495 3 erik.arvidsson 2014-05-08 22:02:35 +0000 Fair enough.