Backslash integrity test

All JavaScript for this page lives in the template. Nothing on this page is a script.

NO RESULT -- the template script did not run at all.

Either the template was not applied to this page, or its script died before reaching the results block. Check the browser console for a syntax error.

1. Template JavaScript

Each row runs a backslash-dependent expression. "STRIPPED" rows are the dangerous ones: the code still ran, it just quietly did something different.

The template never filled this table in.

The template script did not report a raw backslash count.

2. Non-script content in THIS field

Read these with your eyes. They answer whether the pipeline touches ordinary content or only script tags.

2a. Plain text backslashes.
Should read exactly: C:Userstestfile.txt
Actually reads: C:Userstestfile.txt
If the second line is missing its backslashes, non-script content is stripped too.

2b. CSS escape, declared in the template.
This marker should be preceded by a curly opening quote: like this
The template sets content: "201C". A curly quote means CSS escapes survive in the template. The literal text 201C means they do not.

3. Consent gating -- template tag vs content-field tag

Two identical bare marketing tags, one authored in the template and one just below this paragraph in the content field. Whichever the pipeline gates is the one that waits for consent; whichever it leaves alone loads and can set cookies immediately. At least one gated tag is what makes the cookie banner appear at all -- a site with none correctly shows no banner.

The template script never filled this in.

4. What each outcome means

Result	What it means for us
Section 1 all INTACT	The template is safe. Since every line of our JavaScript lives there by rule, the bug is close to a non-issue for our builds -- it only bites content-field scripts, which our standard already forbids. Still worth reporting, because it affects every other site on the platform.
Section 1 any STRIPPED	Serious. The pipeline corrupts the one place we are told to put all our code. Every regex, escape sequence and escaped quote we ship is at risk, silently. This becomes a blocker rather than a footnote.
2a loses its backslashes	The rewrite is not script-specific -- it is mangling all content. Widens the bug considerably: any documentation page, code sample or Windows path we publish is wrong.
2b shows "201C"	CSS escapes are stripped too. Affects typographic content, icon fonts, and any `content:` rule using an escape.
Both tags GATED	Correct. The manager catches marketing tags wherever they are authored, and the banner appears because there is something to ask about.
Template tag NOT gated, content tag gated	A compliance gap. Any marketing tag placed in the template loads and can set cookies before the visitor answers the banner -- and the template is exactly where a developer would normally install Google Tag Manager sitewide. Report it.
Neither gated, no banner	Gating is not running on this site at all. Check that consent is enabled in the site settings and that the config JSON resolves.

Authoritative check either way: view source on the published page and search for a backslash. The template script counts them from the live DOM and reports it above, but view-source is what goes in the ticket.