-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
transition in custom element #4998
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
<svelte:options tag="custom-element"/> | ||
|
||
<script> | ||
import { onMount } from 'svelte'; | ||
import { fade } from 'svelte/transition'; | ||
|
||
let show = false; | ||
|
||
onMount(() => { | ||
show = true; | ||
}); | ||
</script> | ||
|
||
{#if show} | ||
<p transition:fade> | ||
Fades in and out | ||
</p> | ||
{/if} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
import * as assert from 'assert'; | ||
import './main.svelte'; | ||
|
||
export default async function (target) { | ||
target.innerHTML = '<custom-element></custom-element>'; | ||
|
||
// wait one tick in order for styles to be applied | ||
await Promise.resolve(); | ||
|
||
const el = target.querySelector('custom-element'); | ||
const style = el.shadowRoot.querySelector('style'); | ||
|
||
assert.ok(style); | ||
assert.ok(style.sheet); | ||
assert.equal(style, el.shadowRoot.firstElementChild); | ||
assert.equal(style.sheet.cssRules.length, 1); | ||
assert.equal(el.shadowRoot.__svelte_stylesheet, style.sheet); | ||
} |
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 found a weird behaviour doing so, let's suppose we have a transition on hover on an element, if the element on which we want to apply the transition is directly a child of a
shadow-root
element it will be okay, if otherwise it's a child of a regular DOM node (let's say a div) it will keep on appendingstyle
tags on each hover. Looking recursively for aparenElement
to get to the root of thewebComponent
solves the issue.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.
Interesting, thanks. Could you show me your code so I can have a look as well?