Home › Forums › Support › JS conflict This topic has 4 replies, 2 voices, and was last updated 8 years, 3 months ago by Tom. Viewing 5 posts - 1 through 5 (of 5 total) Author Posts November 27, 2015 at 10:29 pm #156206 I.S. Hi, At the bottom of js/navigation.js is the function: jQuery( '.dropdown-toggle' ).click ... The class “dropdown-toggle” is a somewhat common class used in other plugins, such as DWQA, which is creating conflicts/unexpected behavior. Could the selector be made more specific? I believe “.main-navigation .dropdown-toggle” should work just fine. Thanks in advance! November 27, 2015 at 10:41 pm #156213 TomLead Developer Lead Developer Tough one, as the Secondary Nav uses the same snippet of code and doesn’t have the .main-navigation class. I’ll find something common between the two and get it implemented into the next version π Thanks! December 2, 2015 at 12:06 am #157203 TomLead Developer Lead Developer Alright, I ended up just using: nav .dropdown-toggle. This works on all of our nav elements, and shouldn’t cause issues with other plugins unless they’re adding their own navigation elements. Let me know π December 2, 2015 at 7:12 pm #157526 I.S. Excellent! Many thanks! December 3, 2015 at 12:16 am #157559 TomLead Developer Lead Developer No problem! Thanks for bringing it to my attention π Author Posts Viewing 5 posts - 1 through 5 (of 5 total) You must be logged in to reply to this topic. Log In Username: Password: Keep me signed in Log In