-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
z-index calculation should not stop at first element #710
Conversation
i guess that when calculating proper z-index for the datepicker, we should find the max z-index value of parents() and not stop at first related to uxsolutions#533 uxsolutions#170 uxsolutions#683 uxsolutions#678 uxsolutions#656 uxsolutions#665 uxsolutions#634 uxsolutions#621 uxsolutions#609
I've seen some solution here: http://stackoverflow.com/a/5680879/932965 Anyway I haven't had time to check if it have been optimal and set z-index manually. |
👍 See also #876 |
Our production code is riddled with :
When will this issue (#569) be handled ? |
Thanks @fadomire! |
thanks but #876 should have been merged instead of mine |
@acrobat #876 is basicly the same as mine, but cleaner and clearer to read. But you are right for some IE version the map and slice method would crash, did not thought about that. But maybe replacing the native map and slice in #876 with the jquery one would solve the cross browser issue while being clearer |
thx |
@Offirmo Thanks for your solution, it works for me. |
i guess that when calculating proper z-index for the datepicker, we should find the max z-index value of parents() and not stop at first
related to #533 #170 #683 #678 #656 #665 #634 #621 #609 #464