Changelog

v7.13.0 — 2026-03-25

This release officially aligns the current plugin build on Remote Tab Opener Manager v7.13.0 and refreshes the extension popup with a cleaner, more structured interface.

Popup UI refresh

• The extension popup now uses a dedicated stylesheet for a cleaner separation between structure, behavior, and presentation.
• The interface has been reorganized into clearer panels and sections for faster reading and easier control.
• The controlled-tab display area is now presented more clearly through the Current tab displays : section.
• Favorites and allowed-domain controls are grouped more cleanly for everyday use.

Versioning and plugin consistency

• The current extension manifests are aligned on version 7.13.0.
• The popup footer continues to read its displayed version dynamically from the manifest.
• The plugin changelog has been updated so the current release reference now matches the shipped extension version.

Branding

• The current plugin branding/logo is now reflected in the extension interface.
• Website-wide logo propagation remains separate and is not part of this plugin release note.

v7.12.1 — 2026-02-18

This is a small follow-up release to v7.12.0, focused on API usability and documentation correctness, without changing the overall behavior of the extension.

RTOForm helper API

• Status listeners hardened: iterates over a snapshot of listeners to avoid edge-cases when callbacks add/remove listeners during dispatch.
• Docs alignment: documentation pages updated to reflect the status channel (tabStatus) and the recommended onStatus/waitForStatus usage.
• No breaking changes: message naming remains compatible (camelCase canonical + legacy UPPERCASE mapping).

Notes

• No new permissions, no telemetry/data collection; local-only and gated by allow-list.

v7.12.0 — 2026-02-17

This release focuses on API/message naming consistency, safer DOM operations, and stronger MV3 (Chrome) + Firefox reliability, while preserving behavior and adding compatibility bridges where needed.

Message/API naming consistency (canonicalization)

• Standardized internal message type naming to a consistent camelCase scheme.
• Legacy UPPERCASE message types are mapped to camelCase and still supported during migration.

Allowlist:
ALLOWLIST_ADD      -> allowlistAdd
ALLOWLIST_LIST     -> allowlistList
ALLOWLIST_CHECK    -> allowlistCheck
ALLOWLIST_REMOVE   -> allowlistRemove
ALLOWLIST_NEEDED   -> allowlistNeeded

UI / events:
CONTENT_READY            -> contentReady
CONTROLLED_BANNER        -> controlledBanner
CONTROLLED_BANNER_STATE  -> controlledBannerState
PROMPT_ALLOW_DOMAIN      -> promptAllowDomain
DEBUG_DUMP               -> debugDump
POLICY_STATUS            -> policyStatus

content.js (content script) — bridge + command hardening

• Preserved canonical admin-page → content messaging (type:"command") with stronger normalization.
• Maintained pass-through model for background actions (open/navigate/close/listTabs/adopt/release/allowlist/favorites...).
• Kept legacy DOM aliases via a compatibility bridge (without bringing back deprecated global aliases).
• Safer HTML extraction: redacts sensitive values (password/hidden/credential-like inputs) and sanitizes outerHTML.
• Unified command result shaping (ok/error envelope) and improved error propagation when background does not respond.
• Overlay utilities stabilized (idempotent creation, clean cancel/restart animations, preserved label options).

content_master.js (UI content) — controlled banner + allowlist prompt UI

• UI-only content script: renders the controlled-tab banner only when instructed by background.
• Minimize into draggable pill; mirrors state back (controlledBannerState) and is now superseded in v7.13.0 by background-owned per-tab banner state.
• Allowlist toast UI reacts to allowlistNeeded/promptAllowDomain; in v7.13.0 the page-driven add flow moves to allowlistAddRequest with confirmation on the master tab.
• Encapsulated UI: CSS injected once (idempotent), high z-index, no dependency on host CSS.
• UI fixes: real <button type="button"> for minimize; removed duplicated logging.

background_core.js — robustness + policy/allowlist + queueing

• Improved MV3 + Firefox reliability: per-tabKey FIFO queue gated by contentReady + timeouts to prevent stuck requests. In v7.13.0, openTab is serialized per tabKey to prevent duplicate tabs.
• More robust relay-to-content: explicit errors for uninjected/uninjectable URLs; injection+retry when listener isn’t ready.
• Hardened URL allow-policy enforcement: HTTPS-only, blocks file:// and javascript:, respects localhost/LAN flags.
• Allowlist improvements: consistent host normalization, dedupe/cleanup, merges legacy keys (allowedDomains + allowlist). v7.13.0 also adds the request/confirm/reject flow for page-side allow-list additions.
• Controlled tab bookkeeping stabilized (controlledTabs, keyToTabId) and v7.13.0 moves master tracking to a per-tab mapping instead of one global master.
• Favorites: stricter URL normalization + dedupe + stable labeling.

Migration / compatibility notes

• Supports both new camelCase names (preferred) and old UPPERCASE names (legacy) during rollout.
• Goal: eliminate mixed-style usage while keeping older pages functional in mixed deployments.

v7.11.4

• This update fixes the focusTab behavior (bugfix).
• The codebase has undergone a significant internal refactor/rewrite for stability/performance; no new user-facing features beyond the bugfix.
• No new permissions, no telemetry/data collection; local-only and gated by allow-list; no cookie access, no arbitrary eval.
• Docs cleanup: removed legacy/compat snippets — all examples target v7.11.4.

v7.11.2

• Single, modern page↔extension bridge: request/response correlation via requestId and bounded timeouts (see RTOForm helper).
• Website install detection: uses RTOForm.detect() (no legacy “ping/pong” or deprecated message types).
• Docs cleanup: removed legacy/compat snippets — all examples target v7.11.2.