CLAUDE WATERMARK REMOVER · DESTINATION TEST
Does trimEnd remove both margins after cleaning?
No. The test removes trailing spaces while preserving the two leading spaces.
What the test establishes
The synthetic field deliberately includes two ASCII spaces on each side. The callback removes the interior marker and retains the margins. A destination trimEnd call removes only the right margin. Choose a margin policy before comparing fixed-layout fields; removing leading spaces can change indentation that the cleaner intentionally leaves intact.
Reproduce the observation
Save tested-app.js and reproduce.cjs together, then run node reproduce.cjs. Compare its output with the recorded observation. The harness executes the actual homepage callback in a minimal DOM and records its resulting field values and method calls. Destination operations run in Node.js; the homepage DOM is a controlled substitute. Runtime: v24.22.1. No submitted text or genuine Claude output is used.
{
"cleaned": " A ",
"end": " A",
"both": "A"
}Capability boundary
This fixture tests ASCII margins and an explicit destination method. It does not measure every Unicode whitespace or suggest that trimEnd removes invisible characters inside text.
This Claude watermark remover edits a small selected character set. These callback observations do not establish authorship, detector scores, statistical-watermark removal or end-to-end browser behavior. For real work, keep the original and compare the exact result at its destination.
Primary material and next step
The tested first-party source snapshot and complete harness are the primary material for this page. For broader scope, read invisible Unicode versus AI watermarks, or return to the cleaner.