Skip to content
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

Range input issues with MS Edge #1

frank-laemmer opened this issue Jul 3, 2018 · 0 comments

Range input issues with MS Edge #1

frank-laemmer opened this issue Jul 3, 2018 · 0 comments


Copy link

@frank-laemmer frank-laemmer commented Jul 3, 2018

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant