- From: Eric Willigers via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Dec 2018 00:18:08 +0000
- To: public-css-archive@w3.org
Another example is CSS Selectors 4 `:is(:not(...))` When the spec has no limits, implementations are forced to make their own choices between - having well known and ignored stack overflow crashes, e.g. on fuzzer-generated input. The smallest example that crashes can change when moving to a different compiler version or when adding an unrelated feature. - not using their implementation language's support for recursion, complicating their code and increasing the development cost of future features. - choosing their own limits and making an intentional choice to fail any WPTs that go further. -- GitHub Notification of comment by ewilligers Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3462#issuecomment-449184899 using your GitHub account
Received on Friday, 21 December 2018 00:18:09 UTC