You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please go to the demo page (note the loading order, the latest versions of all libraries being used and noConflict() already in place).
Drag the browser screen small until the menu items disappear and the menu icon appears.
Click the menu item to open the dropdown menu, and click it again to close it back up.
The menu immediately disappears (without the normal smooth slide-up effect) and can't be dropped down again (Mac OS Lion Chrome) or can be dropped down again, but upon making the browser wide again the menu items never appear back (Mac OS Lion Firefox).
I boiled this behavior down to line 3139 of mootools-more.js in their hide() function, which apparently is being run (something a simple alert() right before line 3139 would show). Is MooTools perhaps attaching this hide() event too aggressively to DOM objects?
This issue was posted earlier on the Twitter Bootstrap bug tracker (twbs/bootstrap#3436), where it was referred to as a potential problem in MooTools.
Problem: When both jQuery and MooTools are loaded, Twitter Bootstrap seems to be running code from the MooTools library.
Demo (minimal): http://www.tweepixels.nl/bootstrap/
I boiled this behavior down to line 3139 of mootools-more.js in their hide() function, which apparently is being run (something a simple alert() right before line 3139 would show). Is MooTools perhaps attaching this hide() event too aggressively to DOM objects?
This issue was posted earlier on the Twitter Bootstrap bug tracker (twbs/bootstrap#3436), where it was referred to as a potential problem in MooTools.
Regards,
Theo
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: