Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference Target Tracking Issue #1086

Open
6 tasks
dandclark opened this issue Nov 27, 2024 · 4 comments
Open
6 tasks

Reference Target Tracking Issue #1086

dandclark opened this issue Nov 27, 2024 · 4 comments

Comments

@dandclark
Copy link
Contributor

dandclark commented Nov 27, 2024

Filing this issue as a central place to track open questions about reference target.

Blocking Phase 1:

Blocking Phase 2:

  • An issue still needs to be filed on this, but we received feedback at TPAC 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.
  • In phase 2, how can an author indicate that references for a given property should not be forwarded?

Non-blocking:

For Chromium implementation TODOs, see here.

See also whatwg/html#10707.

@Westbrook
Copy link
Collaborator

As of 2024Q4, the following tasks are NOT blocking an initial release, right?

@dandclark
Copy link
Contributor Author

As of 2024Q4, the following tasks are NOT blocking an initial release, right?

Right. I've edited the original comment to make this clearer.

@alice
Copy link
Member

alice commented Nov 28, 2024

I filed an issue for the name bikeshed: #1087

@alice
Copy link
Member

alice commented Dec 5, 2024

Apologies if I missed an earlier resolution on these issues, but I have come across some other potential blockers for phase 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants