-
Notifications
You must be signed in to change notification settings - Fork 300
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
valueBox class not always being cleared #106
Comments
I've seen this bug before but had hard time reproing it -- this drove me crazy! Thanks so much, I'll see if I can get it fixed based on your example. |
@jjallaire This bug seems to be back. I reused the the example presented here and got the behavior described by @davidski above. I thinks it's because the value box class are now I tried to fork the repo and modify the lines that changed in 5bd738c but couldn't find the file |
Looks like I found a way to fix it with these modifications by adding: Result:
I'll make a PR ! |
When setting the
color
attribute based upon the value of the input tovalueBox
when using the Shiny runtime, the valuebox div does not always have the previous class removed and winds up with twobg-*
classes applied (and the wrong value taking precedence).To reproduce:
danger
and see the color change as expectedsuccess
and see the color change as expecteddanger
again and see the color not change. Inspecting the HTML shows two classes now applied.Example code as follows:
The text was updated successfully, but these errors were encountered: