- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Sun, 28 Jun 2015 18:07:01 -0400
- To: www-style@w3.org
On 06/28/2015 04:21 PM, Simon Sapin wrote: > On 27/06/15 10:47, fantasai wrote: >> I'd argue that we may want to >> allow implementations to use context-specific parsing rules as >> well, if they want to go that route instead, so the UA would be >> allowed to either accept or reject u+a/**/rea. (A full CSS parser >> might not want to do that, but a Selectors parser shouldn't have >> to deal with unicode-range token munging. Ditto An+B, now I think >> about it.) > > Allowing a different behavior without mandating it reduces interop, > and this doesn’t seem to be a good enough reason to do it. The cases where there wouldn't be interop are just weird edge cases like u+a/**/rea, right? I don't think interop on that case is worth imposing the complexity of a CSS-token-munging parsing model on all non-CSS implementations of Selectors. ~fantasai
Received on Sunday, 28 June 2015 22:07:34 UTC