Support
XML Viewer 1.0.0
The fastest way
Write to hello@madeit.ist. If a particular document is behaving badly, the address it is served from is worth more than any description of it — and if it is not public, the first twenty or so lines usually are.
Say which version you are on as well. It is printed under the extension’s name in chrome://extensions.
Usual questions
It did not take over my XML page
If the document ships an XSLT or CSS stylesheet — most sitemaps do — the extension deliberately leaves it alone, because the author meant that page to be rendered. Click the toolbar button to switch that one page to the tree, or turn on “Take over even when the document has a stylesheet” in settings to make it the default.
The feed shows as plain text
Some endpoints send XML with a text/plain content type. The extension recognises those and renders them anyway, unless you have switched off “Also handle XML served as text/plain”. If a page is still plain text after that, it is probably not well-formed XML — open it and the error view will say where.
Local .xml files do nothing
Chrome withholds file:// access from every extension until you grant it. Go to chrome://extensions, open XML Viewer’s details, and switch on “Allow access to file URLs”.
I need it to keep out of one site
Settings → “Never take over these sites”, one host per line. example.com covers its subdomains too, and *.internal.example.com covers only the subdomains. The content script stops before doing anything on those hosts.
The Source tab opened as raw bytes, not formatted
On a large document, formatting means building the whole file again as a string, which takes seconds and blocks while it does. So Source starts on the original bytes, which is instant, and formatting is one click away when you want it.
A huge feed opens mostly collapsed
Expanding every record of a fifty-thousand-item feed would build over a million rows before you saw anything. The first few thousand records open normally and the rest wait until you click them. “Expand depth on open” in settings controls how deep that goes.
Search felt slow the first time
The first search reads every element in the document — on a twenty-megabyte feed that is around three quarters of a second. Every keystroke after it narrows the previous matches instead of starting again, so it stays instant from there. Clearing the box and starting a new word pays the cost once more.
What the extension stores, and what it refuses to collect, is set out on the privacy page.