Tab Atkins Jr.

If it was easy to block I'd prefer to not allow that, but I'm fine with allowing it if needed, yes.

> But there's no point in trying to reason with you on that subject, is there? Reminder that the [W3C Code of Conduct](https://www.w3.org/policies/code-of-conduct/) is enforced in this repo.

More directly, look at *both* of the images in the OP. The *second* one is readable, because it uses a partially-transparent black + a blur. The *first* is completely unreadable,...

No, we don't want to distinguish abspos vs fixpos in that way, because a fixpos can *act* like an abspos given certain ancestor styles. What you actually care about is...

All right, (2) is solved by restoring the text I'd accidentally deleted earlier, and restored when fixing #11170. I solved (1) by just copying the same text over, as the...

The names were already changed from `auto`/`opposite`; the intention is that they attach you to the relevant edge that puts you "inside" or "outside" the anchor. In particular, `inset: anchor(inside);`...

> I would be much more in favor of shipping attr() support with a whitelist Yup, some of our internal security folk were finally able to give a "probably okay"...

See #5092 for discussion on the security concerns, I just made some edits and posted a comment today. (And no, I doubt data urls would be safe to allow, since...

> Requiring using data- attributes for custom elements would feel weird. Note that `data-*` attributes are *not* safer to use, as this comment (and several others) seems to be implicitly...

@domenic Thank you, that's a much better summary! I agree with all of this. @annevk Would you prefer holding it as a Good First Project, then? Would you mind if...