Use QCDR Page Scan to Catalog Notable Frontend Output

Page Scan is a read-only inventory of notable output already present in the current private Discovery page. It helps you find headings, text, links, buttons, media, form controls, QCDR Token regions, and useful render context without clicking every element individually.

Page Scan does not crawl the site and does not query stored Joomla source by itself.

Run the Scan

  1. Launch Discovery on the frontend page you want to inspect.
  2. Choose Scan this page.
  3. Review the summary counts and result list.
  4. Use the scan filter to narrow by kind, visible value, element descriptor, or source context.
  5. Choose Explain This Output on a result when you want full evidence analysis.

If Dynamic DOM Watch is currently running, QCDR stops the watch before Page Scan and leaves its collected results available.

What Page Scan Catalogs

The scan classifies notable visible elements into Text, Heading, Link, Button, Media, Form, and Token results. It can also display:

  • PROVEN QCDR Token/runtime-boundary context;
  • component or module render-region context;
  • LATE DOM badges for elements already observed changing by Dynamic DOM Watch;
  • the number of QCDR Rules matched on this request;
  • a page-asset count covering scripts, stylesheets, and images.

The Scan Is Deliberately Bounded

QCDR inspects at most 1,800 page elements and keeps at most 240 de-duplicated scan rows. The result panel displays up to the first 120 filtered rows at once; use the filter to narrow a larger result set.

These limits keep the private browser tool useful on large pages without turning it into an unbounded DOM inventory.

What Page Scan Does Not Prove

A result such as Route com_content/article is context, not exact source proof. Page Scan intentionally does not perform stored article/module/language/template lookups for every row. That heavier evidence lookup begins only after you choose Explain This Output.

When Page Scan Is Most Useful

  • A page contains many similar buttons or labels and you need a quick catalog.
  • You want to locate QCDR Token output or component/module render boundaries.
  • You need to compare static output with a previous Dynamic DOM Watch.
  • You know the kind of output but not which element should become the Rule target.

After finding the right row, move into Explain This Output and review the actual evidence/fingerprint before drafting a Rule.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.