- From: Peter Linss <notifications@github.com>
- Date: Wed, 11 May 2022 08:41:18 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 11 May 2022 15:41:30 UTC
We have concerns about the parser change. We understand (and don't disagree with) the reasoning, but feel that parser changes need to be a 'big deal' and question if the benefits really outweigh the cost. We are breaking a promise here and that should only be done when there's a significant benefit. It's not clear the benefit is here. We're not saying no, but more of 'tread carefully'. In the longer term, we'd like to see a declarative mechanism that allows this kind of parsing behavior change to be added to HTML in a forward-compatible way. (e.g. a meta tag that defines behavior changes, or a micro-syntax in the open tag, or ??). We can foresee wanting this kind of behavior in other yet to be defined tags and if we're going to change the algorithm, better to do it once rather than over and over. (It would also be nice to support new self-closing tags.) -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/714#issuecomment-1123944700 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/714/1123944700@github.com>
Received on Wednesday, 11 May 2022 15:41:30 UTC