When a wall gets through.

Start with the checks below. Sites redesign their consent walls often, and a new one can slip past Tacet until it learns to recognise it.

Report a problem

Open an issue on GitHub with the page address and what you see. Issues are public: do not include personal information.

Quick checks

A wall is still on the page

Open Tacet’s popup from the toolbar and press Zap now: it hides whatever still covers the page and unlocks scrolling. If that works, report the page, so that Tacet learns to do it on its own.

Something I opened disappeared

Tacet leaves alone what you open with a click, but it can misjudge a window that takes a long time to appear. Press Undo on this page in the popup, or switch Tacet off for the site, then report the page.

The page still will not scroll

Press Zap now. Some sites block scrolling with scripts that cancel the mouse wheel or touch gestures; Tacet cannot undo those yet.

I want to give my consent on a site

Click the site’s own cookie settings link, usually at the bottom of the page: Tacet steps aside and the site’s dialog comes back. You can also switch Tacet off for that site from its popup.

The article is still cut short

Tacet removes what stands in front of a page, not content the site has left out. Articles reserved for subscribers stay reserved.

Tacet does nothing on a page

Tacet runs only on web pages: not on the browser’s own pages, on extension stores, or on files opened from your computer, and not inside frames embedded in a page. Check in its popup that it is active for the site.

When reporting a problem

The page address.
Your browser and its version, and Tacet’s version from the browser’s extensions page.
What you expected to happen, and what happened instead.
The list in Tacet’s popup, which says what it hid on the page and why.

Never include passwords, cookies or personal information. For how Tacet handles data, read the privacy policy.