Nolan Lawson

> Using the `elementtiming` attribute directly on a shadow element would expose that internal element's timing to the global timeline. This would expose multiple elements from the shadow root, if...

Ah, I misunderstood. I thought that (like cross-root ARIA), the timings would need to be re-exported up the tree (**option 2**). If they are exported globally (with namespacing), then that...

Most of the errors do look like this. It's not guaranteed, though. There are certain cases where the errors are meaningful and we expect people to handle them themselves. In...

@kzheng-sfdc Can you explain more what you mean?

@rochejul The LWC team (my team) owns this.

> We do not intend for Jest to be used to test SSR & component hydration. We [do have SSR testing capabilities](https://github.com/salesforce/lwc-test/tree/master/packages/%40lwc/jest-preset#lwc-components-rendered-on-the-server).

BTW there is more discussion about how the accessible name spec interacts with shadow DOM in https://github.com/eps1lon/dom-accessibility-api/issues/768 and https://github.com/w3c/accname/issues/51 .

What do you mean by "provided implicitly"? Does this overlap with [`ElementInternals`](https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals)?

Is this the same as [reflection/exporting](https://github.com/leobalter/cross-root-aria-delegation/blob/main/explainer.md#21-reflection)? In your example, the `for` IDref is pointing down into the shadow root. (As opposed to delegation/importing, where it points out of a shadow...

Opened a PR: https://github.com/leobalter/cross-root-aria-delegation/pull/28