- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Sun, 22 Apr 2018 04:29:15 +0000
- To: public-css-archive@w3.org
So https://github.com/w3c/csswg-drafts/commit/2821e3f7245b4644225f8b1e54c371353aed12f2 switched from a totally-not-what-browsers-do sequence to an interface that still isn't what browsers do... I should note that at one point I supported making pretty much all arraylikes without a named getter ArrayClass. That was before it became clear that some browsers have no plans to ever implement ArrayClass on anything. At this point the best path to interop is to never use LegacyArrayClass. -- GitHub Notification of comment by bzbarsky Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2601#issuecomment-383354574 using your GitHub account
Received on Sunday, 22 April 2018 04:29:20 UTC