You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the overall approach to the semantic HTML and CSS.
However, when working with WebComponents there are some troubles.
For instance, when using dialogs, it's often the parent component that decides if the child component should be in a dialog.
So it's parent -> dialog -> child -> header/div/footer.
In that scenario, the CSS won't work as the header/footer does not direct children to the dialog. Isn't it enough to style any header/footer in a dialog? Having more than one seems to a pretty bad dialog design :)
The text was updated successfully, but these errors were encountered:
I love the overall approach to the semantic HTML and CSS.
However, when working with WebComponents there are some troubles.
For instance, when using dialogs, it's often the parent component that decides if the child component should be in a dialog.
So it's parent -> dialog -> child -> header/div/footer.
In that scenario, the CSS won't work as the header/footer does not direct children to the dialog. Isn't it enough to style any header/footer in a dialog? Having more than one seems to a pretty bad dialog design :)
The text was updated successfully, but these errors were encountered: