-
-
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
custom-file selector isn't a valid CSS value since upgrade to beta3 #25127
Comments
We need to update the Migration docs—that Sass map has changed. See our |
afomera
added a commit
to ProctorU/hootstrap
that referenced
this issue
Dec 30, 2017
The SCSS map for $custom-file-text has changed. Per this GH issue: twbs/bootstrap#25127 I looked at the _variables.scss file to find the updated map.
Yes, its working now. Even better, so much simpler. Thanks for the quick response.
… Op 30 dec. 2017, om 03:15 heeft Mark Otto ***@***.***> het volgende geschreven:
We need to update the Migration docs—that Sass map has changed. See our _variables.scss file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#25127 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWNN1C0yBMLeWzvmMOY449Pq81Da7PTks5tFZzegaJpZM4RPbP7>.
|
mdo
added a commit
that referenced
this issue
Dec 30, 2017
XhmikosR
pushed a commit
that referenced
this issue
Dec 31, 2017
licatajustin
pushed a commit
to ProctorU/hootstrap
that referenced
this issue
Jan 5, 2018
The SCSS map for $custom-file-text has changed. Per this GH issue: twbs/bootstrap#25127 I looked at the _variables.scss file to find the updated map.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a Ruby-on-rails project (using the Bootstrap gem) where I use the custom file selector text according to the documentation:
After upgrading from beta 2.1 to beta 3 I now get the following error:
As I'm using SASS I ensured not upgrading any other gem but Bootstrap to exclude other gems from being the problem gem.
I could not find any upgrade or migration information on this specific component. So I suspect it is a bug. Here is my error:
The text was updated successfully, but these errors were encountered: