-
Notifications
You must be signed in to change notification settings - Fork 313
Add reference target to shadow root #1353
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
Open
dandclark
wants to merge
4
commits into
whatwg:main
Choose a base branch
from
dandclark:dandclark/reference-target
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e06f903
Add reference target to shadow root
dandclark 9ce89ff
Merge branch 'main' into dandclark/reference-target
dandclark 496ccae
Make order consistent with other ShadowRoot properties
dandclark 64676d6
Add type declaration for ShadowRoot reference target
dandclark File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not quite sure, if it is good to have this v1 API and then more complicated v2, or could we have just one API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or whether this API should look a bit different so that adding v2 would feel a bit less weird.
Just as an example, not proposing this... what if this was more like
attribute ReferenceTarget referenceTarget;
and then
interface ReferenceTarget {
attribute DOMString? default;
// v2 would add more attributes
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is the sketch for v2? We should at least have an idea on what this transition will look like. Did someone write that out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the slow follow up here -- v2 is sketched out at https://github.com/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.md#-phase-2-shadowroot-referencetargetmap-attribute.
That examples in that proposal imply an IDL like this:
So the behavior would be that
shadowRoot.referenceTarget
is the default, and is overridden by any non-null values in theReferenceTargetMap
.I can see an argument for grouping everything together into a single
ReferenceTarget
interface, but I do think it'd be nice to keep the simple case simple and allow a directshadowRoot.referenceTarget = "target"
rather than requiring the additional indirectionshadowRoot.referenceTarget.default = "target"
. Either design seems basically reasonable though.