Imperative Slot Assignment #55
Merged
Conversation
This file contains 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
thescientist13
changed the title
Westbrook
reviewed
Sep 5, 2022
| </section> | ||
| <section> | ||
| <h3>Key Scenarios</h3> | ||
| <p>---</p> | ||
| <p>Some of the scenarios called out in the proposal include not having to pre-compute the slot names ahead of time, as well as being able to conditionally load content into a slot.</p> |
There was a problem hiding this comment.
Would be cool if @cdata might be able to share whether this API does nice things for <model-viewer> dynamic slot situation…
Westbrook
force-pushed
the
report-2022-imperative-slot-assignment
branch
from
fe94fe3 to
38712d5
Compare
github-actions bot
added a commit
that referenced
this pull request
Sep 13, 2022
SHA: 65aba37 Reason: push, by @Westbrook Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated section re: Imperative Slot API.
Aside from an example and status links and per chats on the topic, mostly just focused on the timeline / roadmap for Safari to ship, as their feature tracker marks this API as supported.
But let me know if we think we should back-fill with all the historical content as well, concerns, dissenting opinions, etc.