Manuel Rego

> and also issues with resolving heights in intrinsic tracks https://bugs.chromium.org/p/chromium/issues/detail?id=750726 Yeah I believe it's due to that Chrome bug.

> https://chromium-review.googlesource.com/c/chromium/src/+/2426423 Yes this is a Chrome bug. It happens with certain zoom levels, or scaling factors. It has been fixed in Chromium 87. As a workaround you might try...

Still no way to generate the intent-to-prototype mail from the new UI (other than using that link `/1?intent`).

There are a bunch of previous discussions quite similar to this one. See for example https://github.com/whatwg/html/issues/6063 which points to https://github.com/WICG/aom/issues/169. Also this delegation proposal: https://github.com/WICG/webcomponents/issues/917 Or other things not directly...

> * Per @mrego, the current implementations in WebKit and Chromium may do this, or they may just make the setter a no-op – needs some investigation. During my tests...

> But still 4th step above happens, and internally the _explicitly set attr-element_ is set, and it points to `element2`. > That's not exposed to the web author, and when...

@nolanlawson should we close this issue and carry on the related work on: https://github.com/leobalter/cross-root-aria-delegation/ and https://github.com/Westbrook/cross-root-aria-reflection/ trying to find a solution for these use cases?

There's also `text-emphasis-color` (as other `text-emphasis` properties seem to affect the layout I guess they're not valid for highlight pseudos). Doing some tests, Chrome and WebKit allows you to change...

Yeah I agree with @fantasai. I don't think `text-emphasis` in general can be applied on highlights due to the layout changes it implies, `text-emphasis-color` should be fine though.

> Add a case to reproduce this issue. > https://jsbin.com/qotevalowe/1/edit?html,console,output In that example if you remove the last line (the one that changes the size to 0x0), then you'll get...