Re: [whatwg/webidl] ObservableArray without assignment (#1027)

The potential concerns raised here sound like they are pretty much the same as [the ones discussed previously](https://docs.google.com/document/d/160HetuBh6sLArif1y-heWpe749b3KPnX54AS-aB8UQ4/edit#heading=h.sm9q9u7af65n). And as before, there are ways to argue both sides. Since the previous discussion also came to a consensus (https://github.com/WICG/construct-stylesheets/issues/45#issuecomment-825055766) with resulting [landed spec update](https://drafts.csswg.org/cssom/#ref-for-idl-observable-array), I think it only makes sense to conclude the same in this case and close this issue as no-change.


> What other APIs are slated to be switched over to ObservableArray? What kinds of patterns in the wild are used with those APIs today?

This is a great question. One potential answer is that `adoptedStyleSheets` has been [implemented in Chromium for several years now](https://developers.google.com/web/updates/2019/02/constructable-stylesheets), with [usage amounting to 13%](https://chromestatus.com/metrics/feature/timeline/popularity/2846) of all [shadow DOM usage](https://chromestatus.com/metrics/feature/timeline/popularity/804), and it **uses an assignable interface** exactly as is proposed. However, [the bug tracker shows zero reported bugs](https://bugs.chromium.org/p/chromium/issues/list?q=adoptedstylesheets&can=1) about the copy semantics of an assignable `adoptedStyleSheets`. While this doesn't mean there aren't people getting confused by this aspect of the feature, it does mean that none of their confusion has risen to the level it takes to report a bug. Perhaps the fears about developer confusion are just hypothetical? Certainly good documentation can greatly help as well.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/issues/1027#issuecomment-937286883