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

Ensure fallback setup when manual slots are inserted into shadow DOM #33440

Merged
merged 1 commit into from Apr 1, 2022

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Mar 31, 2022

When a new slot is added to a shadow DOM with manual slot assignment,
while the slot is guaranteed to not have any assigned node, it may still
have fallback content. This patch ensures that the fallback content is
correctly set up, so that it can be correctly rendered, and can be
correctly cleared when the slot gets an assignment.

Test cases:

  • imperative-slot-initial-fallback.html: Tests that the fallback content
    of an imperative slot is correctly rendered if it has no assignment
  • imperative-slot-fallback-clear.html: Tests that after rendering the
    fallback content and then getting an assignment, an imperative slot
    can correctly clear the fallback content

Fixed: 1292292
Change-Id: I74403ab7c6003a9a0203cfdce1c2896f9529499e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3562222
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#988106}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-3562222 branch 2 times, most recently from ce9dbd1 to 7edeb4c Compare April 1, 2022 20:06
When a new slot is added to a shadow DOM with manual slot assignment,
while the slot is guaranteed to not have any assigned node, it may still
have fallback content. This patch ensures that the fallback content is
correctly set up, so that it can be correctly rendered, and can be
correctly cleared when the slot gets an assignment.

Test cases:
- imperative-slot-initial-fallback.html: Tests that the fallback content
  of an imperative slot is correctly rendered if it has no assignment
- imperative-slot-fallback-clear.html: Tests that after rendering the
  fallback content and then getting an assignment, an imperative slot
  can correctly clear the fallback content

Fixed: 1292292
Change-Id: I74403ab7c6003a9a0203cfdce1c2896f9529499e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3562222
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#988106}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants