-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
[Firefox] -moz-appearance property has been removed #22002
Comments
Wait no, we do actually use this over at scss/_custom-forms.scss#L149. |
According to https://www.fxsitecompat.com/en-CA/docs/2017/moz-appearance-property-has-been-removed/ this change has been postponed. Currently Firefox 58 and Chrome 65 do not support appearance and therefore .custom-select does not work as expected. I can see that in https://getbootstrap.com/docs/4.0/components/forms/#select-menu it's working because the styles include both -moz-appearance and -webkit-appearance Can this change be reversed until browsers start supporting it correctly? |
@janekh The source code (SCSS) is not the same as the compiled CSS, in the build process Autoprefixer adds all the required vendor prefixes. Reverting the change is not necessary |
With Typesetter CMS we use scss.php to compile Bootstrap's SCSS from source, togehter with cusom variables and custom scss. But we do not use autoprefixer. Given that, we add the vendor prefixes to the source SCSS in order to make custom forms look O.K. According to caniuse.com, appearance without vendor prefixes will not see the light of day any time soon (as of July 2018). |
https://www.fxsitecompat.com/en-CA/docs/2017/moz-appearance-property-has-been-removed/
The text was updated successfully, but these errors were encountered: