- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Oct 2019 21:37:43 +0000
- To: public-houdini-archive@w3.org
(2), the `arraylike<>;` declaration, would need to be like `maplike<>`/`setlike<>`, in that they *don't* inherit from the corresponding "real" classes, but do automatically (via the WebIDL spec) install all the appropriate methods on themselves. (Note that maplike<> could *not* have been done by inheriting from Map anyway; the fact that you can bypass any checks done by the subclass's `set()` by just using `Map.prototype.set.call` makes subclassing worthless.) But anyway, yeah, I think giving them an array-subclass member would be just fine; if needed we could still give the parent class an iterator over its child array or something. Need to talk with @lilles about what seems reasonable to do in our impl. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/948#issuecomment-545167043 using your GitHub account
Received on Tuesday, 22 October 2019 21:37:45 UTC