Not sure if this is a bug or by design so marking it as a question for now…
When a drawer is toggled in a table, the tr element is decorated with the class ‘nx-item-has-drawer’ based on open/closed.
When the drawer is closed, the class is removed as part of the animation (slideup). When the drawer is opened, the class is applied outside of the animation (slidedown).
This results in the class always being on the tr element when a snippet is invoked from an action. The class is eventually removed when the animation is completed but depending on how tall the drawer is, processor speed, memory utilization, etc. there is no way to know how long it will take.
Does it make sense to put removeClass outside of slideUp similar to the way addClass is done outside of slideDown? This would provide a reliable method for 3rd parties to know drawer status without having to inspect internal data structures.
Possibly the removeClass inside of slideUp was done with a specific in reason in mind?
Row that is marked drawer not open still has nx-item-has-drawer
This topic has been closed for replies.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
