-
Notifications
You must be signed in to change notification settings - Fork 391
Reference Target Tracking Issue #1086
Copy link
Copy link
Open
Description
Filing this issue as a central place to track open questions about reference target.
Blocking Phase 1:
- Reference Target: How to handle invalid ID references? #1071
- Reference Target: Should the
formandlistJavaScript attributes return the host element? #1072 - Reference Target naming #1087
- Reference Target: what type should the
referenceTargetattribute be? #1093 - Reference Target: How should we treat invalid reference targets for relations set via Element IDL attributes? #1089
- Reference Target: Which attributes are in scope? #1091
- Reference Target: How to handle events fired on the reference target by related elements? #1098
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:
- Depending on the outcome of IDREF attributes are fragile and painful to use w3ctag/gaps#2, should something in addition to IDRefs be supported?
For Chromium implementation TODOs, see here.
See also whatwg/html#10707.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels