On Wed, Feb 19, 2025 at 3:44 AM Yoav Weiss (@Shopify) <yoavwe...@chromium.org> wrote: > Could the relevant spec language live in a PR? Having such language would > make it easier to evaluate the gap between the current CSS spec and the > ability to specify this behavior in an interoperable way.
The current appendix should describe the behavior in sufficient detail for that purpose: it details exactly how to construct the caching key and what keys to add, using the specific HTML terms (origin, site) that we're relying on. Official spec text would just be slightly more precise with its terms, but not, afaict, in a way that would affect implementability. This is already more detail than what is specified for our *existing* :visisted behavior, fwiw, which just exists in an MDN page and still leaves many precise details (such as exactly what selectors are allowed) to the imagination. ~TJ -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAWBYDA41VmLR5SWdfAEoKcFDC%3DrT-UDemR2RiTQ4a%2BabjGv7A%40mail.gmail.com.