-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Class bs-placeholder is no longer set on "default" values in 1.13.10 #2272
Comments
I wasn't able to reproduce this issue. Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case (you can use our preconfigured Plunker), and report back with:
|
Sorry @caseyjhol I didn't get back earlier. Compare this Plunk that's on top of v 1.13.9 and this one that's on top of v1.13.12. Basically before when you had (I assume?) empty I assume that it's some kind of side effect of how it was written previously, but it was a nice feature. Ideally we could set this style independent of the |
…doesn't have a set value, option.value falls back to text anyway) (#2272)
@Amunak Thanks for the demos. This fix will be available in the next release. |
Released in v1.13.13! |
Somewhere between 1.13.9 and 1.13.10 the
bs-placeholder
class is no longer set on non-multiple selects. I suspect this change to be the culprit.I need to style the "default" values differently. My selects looked like this in 1.13.9 (all have the "default" / "initial" value, the first one is a multi-select with nothing selected):
Now in 1.13.10 they look like this:
I'm not sure whether this is a bug or if it's intended, but I could really use a way to differentiate the "default" values from the user-selected ones.
Or maybe I'm going wrong about this and don't understand how it's supposed to work? x)
The text was updated successfully, but these errors were encountered: