-
Notifications
You must be signed in to change notification settings - Fork 69
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
Custom Element creates opinionated stylesheet with no option to exclude it. Better extract it as an optional import. #117
Comments
I did the following to isolate the web-component css from global scope: ` class DatePicker extends DuetDatePicker {
} // Define the extended Datepicker as Custom Element |
Is your feature request related to a problem? Please describe.
I added this script in the head:
<script type="module" src="https://cdn.jsdelivr.net/npm/@duetds/[email protected]/dist/duet/duet.esm.js"></script>Datepicker initialized correctly but creates a constructed stylesheet with css selectors which I do not want. For example I think it's a bad idea to have a selector like .is-active .duet-date__dialog-content. It may interfere with other css (for example an open accordion). I have no other choice than to override this css. Another example is that the Datepicker overrides default focus-Style of the browser which I also think it's wrong.
Describe the solution you'd like
Extract the css in own file and make it optional by importing it whenever you want.
Describe alternatives you've considered
Didn't find any solution
Additional context
N/A
The text was updated successfully, but these errors were encountered: