Theme developer breaks this module's jQuery onclick event. The theme developer module is always active when enabled, so DHTML menu and theme developer cannot be enabled at the same time. I know that the theme developer module shouldn't be enabled casually unless you're actively using it, as it messes heavily with the theme engine, but I still think this should be filed as an issue.

I am not sure if it can be fixed - can an onclick event trigger multiple handlers? Otherwise, the documentation could possibly warn of this conflict, or the module could try to gracefully degrade.

Comments

Chill35’s picture

Chill35 commented

I noticed this problem too.

I use Theme Developer and I cannot live without DHTML menu for my admin menu, and was wondering what was wrong with my dhtml_menu installation for about half an hour before looking at the pending 'bugs'.

I disabled the Theme developer.

I don't think it's worth it so much to fix the problem, but it should be documented that they don't work well together.

Chill35’s picture

Chill35 commented

Either on:

- the module configuration page, in a message, 

// TRUE if the module is both installed and enabled.
if module_exists('devel_themer')

or/and

- during installation...

Chill35’s picture

Chill35 commented

Both the Theme Developer and DHTML Menu are *extremely* valuable tools for theme developers.

I think that other people will likely run into the same problem. We'll see.

Thank you!

cburschka’s picture

cburschka
they
commented
Title: Conflict with theme developer » Theme developer removes
Version: 6.x-1.x-dev » 6.x-2.x-dev
Priority: Minor » Normal
Status: Active » Postponed

Devel_themer sprinkles span elements into the HTML code. DHTML Menu uses a strict CSS selector that finds only a elements directly beneath li elements. This is necessary to avoid attaching behaviors to the links in the submenus beneath it. The span element destroys this chain.

I have attempted to fix this by sneaking an extra class into the a element through the localized_options array, but devel_themer interferes with that also. My conclusion is that it is impossible to fix this, but someone else is welcome to try.

cburschka’s picture

cburschka
they
commented
Title: Theme developer removes » Conflict with theme developer

Bad title change.

cburschka’s picture

cburschka
they
commented
Status: Postponed » Closed (duplicate)

This issue will be fixed by the rewrite of DHTML Menu, which works around the strict CSS selector.

#277063: The next generation of DHTML Menu