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
{{ message }}
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.
Therefore the color values are hardcoded by SCSS and the range input can NOt be themed with CSS only for MS Edge. The function "color(color, step)" will use the global colors map. So the range input will look ok, as long as you don't modify any CSS Vars or within a tinted or inverted local theme.
Alternative workaround
MS Edge and Teutonic are not the best friends yet. There are other issues. Use the build from SCSS option and disable CSS var calculations for a better support (but less cool features).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The implementation of the range input
input[type=range]
or better.range
is a bit buggy for MS Edge. CSS Vars are not accepted for styling there:Official bug at MS:
CSS variables don't inherit into range input track, fill, thumb
Current workaround
Therefore the color values are hardcoded by SCSS and the range input can NOt be themed with CSS only for MS Edge. The function "color(color, step)" will use the global colors map. So the range input will look ok, as long as you don't modify any CSS Vars or within a tinted or inverted local theme.
Alternative workaround
MS Edge and Teutonic are not the best friends yet. There are other issues. Use the build from SCSS option and disable CSS var calculations for a better support (but less cool features).
The text was updated successfully, but these errors were encountered: