Closed (won't fix)
Project:
Render Visualization
Version:
8.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Reporter:
Created:
10 Jan 2023 at 08:37 UTC
Updated:
4 Dec 2025 at 16:48 UTC
Jump to comment: Most recent
Comments
Comment #2
anybodyWell comparing both I still think this module is very helpful as it - as the module name says - visualizes the results, while the core
renderer.config.debug: truesimply adds HTML comments.So I'd vote to keep this! :)
Comment #3
dpiCould we at least link https://www.drupal.org/node/3162480 and https://www.drupal.org/project/cache_review from the project page in the meantime?
Comment #4
fgmConfirmed this is much more convenient than comments in markup as comments are mostly useful to check what exists around a given element, while Renderviz allows discovering all that exists in a page, to pinpoint what is bringing a specific tag, context, or max-age.
Comment #5
grimreaperHi,
@dpi, links added to the project page.
So we need to determine if it would be possible to use Core render cache output and only keep the JS for visualization?
That way we will avoid the bug from #2847712: Broken markup
Comment #6
grimreaperThen should the module be reworked to use Core cache debug output and only focus on visualization or the data exposed by the module are more precised than core ones?
Comment #7
grimreaperThanks for your feedbacks. Closing as won't fix.