[WICG/webcomponents] Reference Target Tracking Issue (Issue #1086)

Filing this issue as a central place to track open questions about [reference target](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.md).

- [ ]  https://github.com/WICG/webcomponents/issues/1071
- [ ] https://github.com/WICG/webcomponents/issues/1072
- [ ] An issue still needs to be filed on this, but we received feedback at [TPAC](https://github.com/w3c/tpac2024-breakouts/issues/30#issuecomment-2375176236) and from the TAG that the microsyntax proposed for phase 2 is undesirable. We should reconsider using separate attributes for each property to be redirected.

Good feedback was also raised during the [TAG review](https://github.com/w3ctag/design-reviews/issues/961). There are unresolved issues from this discussion that could be broken out into separate discussions, including:
- [ ] The API name. Are there names besides `referenceTarget` we should consider?
- [ ] In phase 2, how can an author indicate that references for a given property should [not be forwarded](https://github.com/w3ctag/design-reviews/issues/961#issuecomment-2468788538)?
- [ ] Depending on the outcome of https://github.com/w3ctag/gaps/issues/2, should something in addition to IDRefs be supported?

For Chromium implementation TODOs, see [here](https://issues.chromium.org/issues?q=id:346835896%20OR%20parentid:346835896%2B).

See also https://github.com/whatwg/html/issues/10707.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1086
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1086@github.com>