I am the developer of SuperTextSwap. This is a workflow for previewing different wording in your browser while keeping replacement rules limited to the intended page. This article was generated by an AI agent from product materials and the recorded setup. The screenshot available for this post shows rule setup, not a completed replacement result.
Treat scope as part of the rule
A text replacement needs more than an original phrase and a replacement phrase. The same phrase might appear in navigation, an article, a form and another website. Before adding a rule, decide where it should run.
For the first test, choose a public page you control or may use, and choose a phrase in ordinary body text. Avoid payment pages and form submissions while learning the workflow.
- Install SuperTextSwap from its Chrome Web Store listing and review the permission prompt.
- Open an ordinary webpage, then open the extension.
- Enter a short original phrase and a clearly different replacement.
- Select the current-domain scope instead of every page.
- Add the rule, inspect the page, and use Apply now if needed.
- Check a second area on the same page to see whether the scope is broader than you intended.
The recorded setup used “Markdown” and “结构化笔记” on the current domain exportweb.yi7.net. It stopped before adding or applying the rule. That screenshot demonstrates the configuration controls; it is not evidence that replacement ran successfully.
Narrow the target before using regex
The extension provides plain-text and regular-expression matching, with all-page, domain and custom URL scopes. Element selection or a CSS selector can keep a rule inside a particular page area.
Start with plain text when one literal phrase is enough. A regex describes a class of matches, so it needs a larger test set: text that should match, text that should remain unchanged, and similar strings near the boundary. An expression such as item_\d+ can describe names with digits, but whether it is suitable depends on the content and the chosen scope. Inspect the actual page instead of assuming a pattern is safe because it is short.
Selectors have their own maintenance cost. A website redesign can change its markup and make a previously useful selector stop matching. Re-pick the element and retest when that happens.
Understand display changes and recovery
SuperTextSwap changes what your browser displays. It does not edit the source website's server-side content. Rules can follow newly inserted page content, which is useful for dynamic pages but makes scope checks more important.
When you no longer want a replacement, disable or remove the rule and reload the page to restore the source document. Do not assume deleting a rule instantly reverses every existing text mutation. Check that the rule is still disabled after the reload.
Input fields and rich-text content have separate options. Leave them off for a reading-only test. If you deliberately enable input replacement, check the final form value before submitting: text changed in your browser can still be transmitted to the website by a normal form submission.
Rule storage and feedback
Rules use Chrome sync storage. When Chrome synchronization is enabled, the browser may synchronize those rules through its service. Avoid storing confidential phrases unless you have considered that behavior. The website's interactive example is separate from installed extension rules; using the demo does not configure the extension.
Version 0.1.9 provides popup and native Chrome side-panel rule management. Browser support and permission behavior depend on the environment. A useful bug report includes a public test page, the literal text or regex, the selected URL and element scope, and the observed mismatch. Remove private text and account details from the report.
The guide and privacy notes and GitHub project provide installation and feature details. Personal and non-commercial use is free; commercial use requires written permission. Feedback on reproducible matching and page-compatibility problems is welcome.
Top comments (0)