- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Oct 2019 22:23:59 +0000
- To: public-houdini-archive@w3.org
Right, I think it'd be better if we just starting treating the two new Array subclasses as "the thing", and web developers start to have expectations about them. So, in my mind, (1) will generally be better and preferred going forward. Now, whether it's worth the potential churn and compat pain of switching the API surface, is another question, that I would leave up to you as the editor. (2) would certainly make more sense for just preserving the API shape. Although, even then, I'm unsure how we would get the behavior of "inherits from Array.prototype and gets all those methods" given that the classes in question inherit from CSSStyleValue... so maybe (2) isn't applicable here either. -- GitHub Notification of comment by domenic Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/948#issuecomment-543386354 using your GitHub account
Received on Thursday, 17 October 2019 22:24:02 UTC