- From: Olli Pettay <olli@pettay.fi>
- Date: Fri, 18 Dec 2015 19:04:27 +0200
- To: Domenic Denicola <d@domenic.me>, Simon Pieters <simonp@opera.com>, "public-webapps@w3.org" <public-webapps@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Travis Leithead <travis.leithead@microsoft.com>
On 12/18/2015 06:20 PM, Domenic Denicola wrote: > From: Simon Pieters [mailto:simonp@opera.com] > >> Note that it requires liveness. Does that work for a frozen array? > > Frozen array instances are frozen and cannot change. However, you can have the property that returns them start returning a new frozen array. The spec needs to track when these new instances are created. > Changing the array object wouldn't be backwards compatible. (The attribute used to be DOMStringList) >> Maybe this particular API should be a method instead that returns a sequence<DOMString>? Also not backwards compatible. But I'd assume the first option (changing the array) would be less backwards incompatible, so I'd prefer that one. > > That does seem potentially better... Either could work, I think? >
Received on Friday, 18 December 2015 17:05:00 UTC