-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add a vdiff demonstrating delayed content #5312
Conversation
Thanks for the PR! 🎉 We've deployed an automatic preview for this PR - you can see your changes here:
Note The build needs to finish before your changes are deployed. |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
const el = await fixture( | ||
`<d2l-dialog title-text="Delayed Dialog"><${delayedTag}></${delayedTag}></d2l-dialog>`, | ||
{ | ||
awaitLoadingComplete: false |
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.
This is a special configuration option because otherwise the fixture call itself would wait for all the descendants to be loading-complete. In this case, we want to bypass that since we want to make sure that dialog itself waits for them.
Weirdly getting flake with this that I'm not seeing locally -- amazing. Will investigate tomorrow. |
5d9381f
to
5f082b9
Compare
🎉 This PR is included in version 3.79.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This is a precursor to the changes in #5306 that adds an initially-failing vdiff test to demonstrate the problem. Once resolved, this will "go green".