@laoneo we have some problem with this PR
Debug panel works fine in back-end but in front end it seems like this

@ciar4n can you take a look at the debug console in the front end?

And one more thing debug console in admin login is not showing.

Thanks @Anu1601CS. Does reverting this line help https://github.com/joomla/joomla-cms/pull/20061/files#diff-78d82eb8bd4c1f14a8e99e82ada1daf9R355 ?

@laoneo

Does reverting this line help https://github.com/joomla/joomla-cms/pull/20061/files#diff-78d82eb8bd4c1f14a8e99e82ada1daf9R355 ?

No, this make debug console more messy then before this PR.

I think this is not a proper fix for this.

@amone4 @laoneo this PR was wrong. What we need actually is to move the debug module inside the wrapper:

Can you make a new pr for it?

Can you make a new pr for it?

Me ?

Here is what I'm thinking:
in the template:

<joomla-debug><jdoc:include type="modules" name="debug" style="none" /></joomla-debug>

in the plugin:

		echo str_replace('<joomla-debug></joomla-debug>', '<joomla-debug>' . implode('', $html) . '</joomla-debug>', $contents);

That will decouple the markup form the body tag, but it's also a minor B/C break (?)

Let me know if it's ok and then will push the changes in a PR

If you can, would be great. Guess you need to revert this one as well then.

You want to make a CE out of it?

nah, I just wanted to increase specificity without adding id or some weird class...

@laoneo I can but tomorrow and day after tomorrow is my university exam.
After the exam, I take a look on it. :)

@dgrammatiko yes, please make a new pr if you have time. I'm going to revert this one anyway.

Ok will do. By the way I just saw #11840 due to comment in another issue, so maybe will be a good idea to introduce <jdoc:include type="debug" /> and totally decouple the debug from the modules? (not to be done in the comming PR though.. 😃)

@laoneo there you go: #20120