Changes compared to 1.2.0: content.js (audio re-arm logic), popup (site-access notice and button), manifest (version, host_permissions). No new data collection, no remote code; all code unminified.

Why host_permissions is added: the extension's content script is declared for <all_urls> and processes the audio of media elements on the page the user is on. In Firefox, Manifest V3 host permissions are optional and are not granted on update, so for existing users the content script never ran until they clicked the toolbar icon (activeTab). The popup now checks permissions.contains({origins:["<all_urls>"]}) and, if missing, shows a notice with a button that calls permissions.request() inside the click handler. In Chrome the content_scripts match pattern already grants this access, so the notice stays hidden there; host_permissions is listed for consistency and adds no new warning.

What changed in content.js: media elements waiting for a suspended AudioContext are kept in a list, and the extension retries AudioContext.resume() when a media element fires play/playing, when the tab gains focus or becomes visible, on a user action in the page, on the context's statechange event, and when the user switches the extension on in the popup. Previously it only listened for a click, key or touch inside the page, which never happened on restored tabs with autoplaying media.

How to verify (Firefox): install, open the popup — on a fresh install the notice is hidden because access was granted in the install prompt; to see the notice, revoke "Access your data for all websites" in about:addons → Permissions, open the popup again, click "Allow on all websites", accept the prompt. Then open a page with a video (YouTube or x.com) in a new tab without clicking into the page and start playback with the space bar or a media key: the compressor applies as soon as the video plays, no toggling required.

Problem
After a browser start with restored tabs (especially X in Firefox) the compressor stayed inactive although it was switched on. Toggling it off and on in the popup fixed it.

Root cause
The AudioContext is created suspended on restored tabs. The content script waited for a click, key or touch inside the page before attaching media. With autoplay or media keys that click never came. The popup toggle only triggered a rescan, by which time the browser had usually released the context.

I have made the Plugin Free to use and removed the Buy Function....

Bugfix release.

Fixes:
• Resolves audio dropout on embedded videos from sites whose CDN omits CORS
headers (e.g., X / Twitter video overlays). Volume Balance now automatically
switches to a compatible mode on such elements — the master volume slider
still works, but the compressor is skipped on those videos (not technically
feasible due to a browser security limit on cross-origin media).
• Prevents a brief mute on autoplay videos that start before the browser's
AudioContext has been activated by a user gesture.

Simplified to one global compressor + master volume applied on every site (no more per-site
assignments). Fixes a bug where the master volume slider position was loaded from storage but
the actual audio level didn't apply until the slider was nudged. Cleaner UI, smaller code
footprint.