-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Language: English · فارسی
-
Is the extension loaded? Check
chrome://extensions(orabout:debugging). After a rebuild you must press reload on the extension card and reload the Bale tab. -
Is the master switch on? Open the popup; Blur enabled should be on.
-
Are you on the right site? The content script only runs on
https://web.bale.ai/*. -
Is the stylesheet there? In the Bale tab's console:
document.getElementById('bale-privacy-style') // should be a <style> element document.documentElement.getAttribute('data-bale-privacy') // → "active animate hover sidebarText sidebarAvatars …"
If the element is missing, the content script never ran — that is an install problem, not a selector problem.
-
Browser too old? Chrome 111 / Firefox 121 or newer.
Almost always a Bale update renamed something the extension anchors on.
- Options page → Advanced selectors → turn on Log selector diagnostics
- Reload
web.bale.aiand open the console. You get a table of every selector and how many elements it matches. Rows with0are the dead anchors. - Either add a replacement yourself under Advanced selectors, or open an issue with that table — the bug form asks for it.
To find a replacement selector yourself, see Selector Maintenance.
Run the leak scan in the Bale page console — paste
tools/leak-scan.js and read the table. It
lists every text element with no blurred ancestor. A clean result contains only
timestamps, unread badges and reply counts.
Anything else is a real gap: please report it.
Bale keeps the last-message preview in the row's title attribute, and the browser
renders that as a native tooltip that no stylesheet can reach. The extension suppresses
it — but only while blurring is on and reveal-on-hover is off, since with hover
reveal on, hovering shows you the row anyway.
If you see a tooltip leaking content in any other combination, that is a bug.
The blur uses a CSS filter, which creates a containing block for
position: fixed children. The selectors are deliberately narrow to avoid that, but a
custom selector you added under Advanced selectors can reintroduce it. Remove your
custom selectors and see whether the problem goes away.
Settings live in your browser's extension storage. They are lost if you remove the extension, clear extension data, or use a fresh profile. Use Export settings on the options page to keep a copy.
Another extension or the OS may have claimed Alt+Shift+B.
Rebind at chrome://extensions/shortcuts or about:addons → Manage Extension
Shortcuts. Note the shortcut is delivered by the browser, so it only works while a
browser window has focus.
Open an issue. The most useful report contains the diagnostics table, your browser version and the extension version — the bug form asks for exactly that, and both tools redact message content before printing.
English — using it
English — working on it
فارسی — استفاده
فارسی — توسعه
Links