- From: Cameron McCormack <cam@mcc.id.au>
- Date: Thu, 16 Jun 2011 11:18:07 +1200
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: public-script-coord@w3.org
Cameron McCormack: > > I would prefer to go the route of disallowing all user defined array > > index properties on objects with indexed properties, as that is > > simpler. Boris Zbarsky: > Hmmm. Any idea how web-compatible that is? If we can get away with > that, I'd probably be ok with it; not sure about other implementors. Hard for me to tell, or search for. I don’t really have more than a gut feeling that it would probably be OK. > > I’m yet to do any testing for named properties. There are > > two interfaces that have [OverrideBuiltins], HTMLDocument and > > HTMLFormElement, and I’m guessing that disallowing all user > > defined properties on objects with [OverrideBuiltins] named > > properties is not feasible. > > Pretty sure it's not for HTMLDocument.... Yeah. I would also be OK with just disallowing non-configurable array index expando properties. At least then it would be consistent with named properties… -- Cameron McCormack ≝ http://mcc.id.au/
Received on Wednesday, 15 June 2011 23:18:44 UTC