- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2025 17:29:52 +0000
- To: public-css-archive@w3.org
It only ever really worked accidentally; I didn't process any of the autolink syntaxes inside of "opaque" elements, of which `<pre>` is one (also script/style/xmp). That is, `<pre>[=foo=]</pre>` was not processed, it was left as plain text. It just happened that `<<foo>>` and `''foo''` syntaxes were handled by a completely different parsing layer (just regexes over the source) and thus didn't know what the context was yet, so they worked. The new parser handles everything consistently. I did still carve out an exception for `<<foo>>`, allowing that to still link, because it's (a) already *extremely* heavily used, (b) obviously useful (non-terminals *often* link to a distant part of the spec or different specs entirely), and (c) impossible for it to accidentally be an innocent usage (because it's super invalid HTML), unlike single quotes. The opt-out for triggering autolinks within opaques is to use the `<l>` element (a bikeshed-specific element meaning "link"). But I realize that `<l>''foo''</l>`, specifically, doesn't work; that's a bug on my part. (Again, wasn't necessary in the old parser.) Let me go fix that. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11579#issuecomment-2627866576 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 January 2025 17:29:53 UTC