Added example at https://drafts.csswg.org/css-content-3/#example-36e84f01
вторник, 8 июля 2025 г. в 20:14:57 UTC+2, jacka...@gmail.com: > On Wed, Jul 2, 2025 at 8:40 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> LGTM2 conditional on two things: >> 1) Removing the "at risk" label from the spec >> > > "At Risk" is a W3C term of art that simply indicates, for legal purposes, > that the WG is allowed to remove that feature from a CR spec without having > to return to WD; the post-removal spec can just be republished as a CR > immediately. It is solely a tool for reducing bureaucracy a little bit. It > does not actually indicate that a feature is risky in any way, or *likely* > to be removed, or have any other legal implications. (Yes, this has been a > persistent source of confusion for decades, but it's never been important > enough for anyone to make an effort to change it.) > > Since the spec isn't even *in* CR yet, it doesn't even give us that > benefit, fwiw. But neither does it hurt us in any way. It's completely > reasonable to have a feature that is currently single-implementation marked > as At Risk, just in case. I don't think there's any chance of it being > removed, but you never know. > > We should not be gating shipping approval on this. > > ~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/6364e395-18db-4494-a75a-8a27741b96b8n%40chromium.org.
