-
Notifications
You must be signed in to change notification settings - Fork 83
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
fix: do not remove menu item component theme #3459
Conversation
2978a3f
to
abf95e0
Compare
}, | ||
{ text: 'foo-1' } | ||
]; | ||
open(); | ||
await nextFrame(); | ||
await nextRender(); |
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.
Changed to use nextRender()
which seems to be needed to make all the nested menus rendered properly when debugging (otherwise the elements are in the DOM but not visible).
@@ -567,7 +579,7 @@ describe('items', () => { | |||
}); | |||
}); | |||
|
|||
it('should override the component theme with the item theme', async () => { | |||
it('should override the host theme with the item theme', async () => { |
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.
Changed to use host
which better describes the actual behavior.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Co-authored-by: Serhii Kulykov <[email protected]>
Description
The
theme
feature (#2401) introduced a regression: removal of thetheme
attribute set on theitem.component
.This PR checks if the component already has a theme to make sure it's preserved.
Fixes vaadin/flow-components#2559
Type of change