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
With maintenance and scalibilty in mind, it would be nice to see these namespaced/wrapped with a .wcDocker-class or something, to bypass the need to edit your stylesheets or override these elements in my own stylesheet, since they are globally applied.
The html and body styles in line 18 also are very global and from my point of view they should only be mentioned in the tutorial-section instead of hardcoding them into the base css.
These are just some thoughts on how to bring more flexibilty into wcDocker...
The text was updated successfully, but these errors were encountered:
He Jeff,
I saw, that in your css, some styles are applied globally to some elements:
wcDocker.css
496: .fa-menu
501: .context-menu-submenu:after
621: .fa-pulse
Themes/default.css
156-173: .context-menu-*
196: input
201: select
205-232: button
With maintenance and scalibilty in mind, it would be nice to see these namespaced/wrapped with a .wcDocker-class or something, to bypass the need to edit your stylesheets or override these elements in my own stylesheet, since they are globally applied.
The html and body styles in line 18 also are very global and from my point of view they should only be mentioned in the tutorial-section instead of hardcoding them into the base css.
These are just some thoughts on how to bring more flexibilty into wcDocker...
The text was updated successfully, but these errors were encountered: