-
Notifications
You must be signed in to change notification settings - Fork 1.8k
allow-clear with theme=bootstrap broken in 0.9.6 #578
Comments
It does not relate to allow-clear, the bootstrap-layout is broken completely: http://plnkr.co/edit/2mQ6S7w01mjKhWUMEf6b?p=preview It was ok in 0.9.2 |
👍 |
1 similar comment
👍 |
👍 The Demo Plunker linked to from the README.md should be updated to use the latest version of select.css and select.js. Then this issue is immediately obvious there.
|
@BP18 Thanks. I just tried adding your two workaround adjustments for version 0.9.6 and it didn't appear to make any difference in the styling. |
It appears that if the allowClear directive is included, there is a conditional This is very frustrating. |
Hi @abobwhite, I'm not using allow-clear, but my workarounds seem to work on the demo page. Here's the Demo Plunker as-is other than upgrading to 0.9.6 so I can reproduce the problem: Here's the same Plunker but with my two fixes added: The padding is still messed up, but at least the text-align and other styles are better. Don't think this is really a proper fix, but hopefully it helps figure out what's going on. |
@BP18 Thanks. I'm confused - isn't this issue surrounding the allow-clear styling? |
@abobwhite, in my first demo Plunker link with just the upgrade to 0.9.6, the Bootstrap theme control is messed up. Without focus on the control, the text is center aligned and the field does not have the other Bootstrap |
@artkoenig, yes I think that is where it broke. Commit 6e94894. Previously the button tag had the |
Slightly tweaked my original fixes and submitted a pull request. |
I tried to test your changeset, but the 'allow-clear' button is still broken. Is it supposed to be fixed by your changeset ? |
That was my understanding as well - it sounds like there are two issues here. Broken bootstrap styles in general as well as broken allow-clear styling for bootstrap. I am most concerned about the allow clear but I'm sure both need to be addressed. |
Yes, I think @abobwhite is correct about there being two (related?) issues here. I'm not using allow-clear and neither does the demo page, so my fix didn't address that part. |
I played around with allow-clear=true and I see the second problem you are mentioning (the X/clear button appearing below the field instead of integrated). I think my pull request addresses the other styling issues and doesn't make the allow-clear issue worse, so hopefully it can be part of a complete solution. Also, there was a recent pull request (#486) that was supposed to add allow-clear support to the bootstrap template, but it doesn't work properly. |
Thanks for all the hard work already put in, a proper fix would be awesome. |
+1 for this |
Meanwhile you can use this little CSS trick:
|
With #606 merged, can you confirm if all works ok now? |
@dimirc That merge doesn't seem to fix the problem. Still looks like the screen grab from the original post. |
@JeromeLam you are right, seams that the problem is the way allow-clear was implemented at #486 I'm checking the code and maybe reverting that PR and do a different implementation |
@JeromeLam based on @bampakoa comment I pushed PR #667 Check updated plunker and I think now should be ok |
Have you checked in firefox ? It seems that the clear button is still below the drop down, however now, it's on the right side. |
FYI: That happens only when the input is so long it overlaps the X button. |
Should be solved with #667 |
http://plnkr.co/edit/yzoAL0PRkOyGHeuMbGj2?p=preview
The text was updated successfully, but these errors were encountered: