Skip to content
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

probable CSS rendering bug with disable/enable #163

Closed
badulesia opened this issue May 4, 2013 · 3 comments
Closed

probable CSS rendering bug with disable/enable #163

badulesia opened this issue May 4, 2013 · 3 comments
Assignees
Labels

Comments

@badulesia
Copy link

Hello.
I'm using disable and enable, and it seems that there is a CSS rendering bug.

At page load, I use an empty and disabled select
<SELECT id='menu_place' size=5 disabled></SELECT>
js
$('#menu_place').selectBoxIt({ defaultText:'some string' });

The select is populated by a function triggered after choosing in another select menu. It contains:
$('#menu_place').data("selectBox-selectBoxIt").remove(); $("#menu_place").data("selectBox-selectBoxIt").add(data); $("#menu_place").data("selectBox-selectBoxIt").enable();

data are some json. Previous options are removed, new ones are added, and the menu is active and works. BUT, it is still rendered as disabled-like.
I suppose that selectboxit js applies some CSS to render the box disabled or enabled: can you check if something is wrong ? some kind of a CSS opacity not set back to 1 when enabling.
If the function is triggered a second time, than the menu is rendering enabled-like.

PS : all is included in a jquery UI accordion.

Thank you

disablebug

@ghost ghost assigned gfranko May 9, 2013
@gfranko
Copy link
Owner

gfranko commented May 9, 2013

Thanks for reporting this! It will be fixed in the next release!

@gfranko
Copy link
Owner

gfranko commented May 10, 2013

This has now been fixed with the v3.5.0 release! You can grab the new JS file here

@gfranko gfranko closed this as completed May 10, 2013
@badulesia
Copy link
Author

Le 10/05/2013 17:35, Greg Franko a écrit :

This has now been fixed with the v3.5.0 release! You can grab the new
JS file here
Thanks. I've tested and it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants