Skip to content

Releases

v1.4

Choose a tag to compare

@RIJUDEVx RIJUDEVx released this 06 Nov 11:50
584cc37

Switch to Classic v1.4 — What's new

The biggest release yet: a full modernization under the hood, a much better in-page experience, and list views that land on the exact Classic view every time.

Highlights

  • Exact list views in Classic — named Lightning list views now open the same ?fcf=… list view in Classic (resolved via the org REST API, with a Classic #fcf selector fallback), and Recently Viewed resolves to the same view instead of dropping you on the object home.
  • Same-tab switching is the default — Classic opens in the current tab; you can opt into a new tab in Settings.
  • Header button you know, better to use — original look restored, now a real <button> with pointer cursor, correct copy behavior, no right-click menu, and a busy state.
  • Popup with live status — the toolbar popup tells you if you're on a record, list, home, or unsupported page before you click.
  • Options page — open-in-new-tab, show/hide the header button, and light / dark / system theme. Settings sync via chrome.storage.sync.

Under the hood

  • Angular 22 (standalone, zoneless — zone.js removed) with the Vite application builder, Vite 8 for the content script and service worker, Node 24, pnpm 12, Vitest 5, TypeScript 6.
  • Repo reorganized into src/ (Angular popup/options), extension/, shared/, public/, and dist/extension.
  • Production build fixed: service worker is bundled, hashed-CSS / CSP inline-style pitfalls removed, and pnpm verify-build checks the manifest matches the output.
  • Permissions trimmed to activeTab, scripting, storage, webNavigation + Salesforce host permissions — no more broad tabs.

Fixes

  • Manifest web_accessible_resources invalid-match-pattern error fixed (origin-only patterns).
  • Switcher &amp; URL bug fixed; content script retries for the Lightning header and re-injects after SPA re-renders.
  • List-view follow-up re-arms after the switcher lands on Classic home, so views resolve to ?fcf=… instead of stopping at /006/o.
  • New-tab about:blank race fixed; API context and list-view results are cached per session.

Open source

  • MIT licensed (LICENSE, Selegic India Private Limited) with PRIVACY.md, SECURITY.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, TRADEMARKS.md, CI/release workflows, and architecture docs (Mermaid) — ready for outside contributions.

Installing

Download extension-build.zip below, unzip it, and load it as an unpacked extension in Chrome:

  1. Go to chrome://extensions
  2. Enable Developer mode
  3. Click Load unpacked and select the unzipped folder

Or install the published version from the Chrome Web Store.

Verifying your install

  • manifest.json reports version 1.4
  • Open a Lightning record, list view, or home (https://*.lightning.force.com) — Switch to Classic Experience appears in the header.

Docs


22 commits since main (efc0236), versioned as 1.4 / 1.4.0. 34/34 tests pass, types clean, pnpm verify-build clean, 0 known vulnerabilities.

v1.3.0

Choose a tag to compare

@RIJUDEVx RIJUDEVx released this 06 Nov 11:53
efc0236

Switch to Classic v1.3.0 — Opens next to your current tab

The last release before the 1.4 modernization.

Changed

  • Classic opens in the tab immediately after the current one — instead of at the end of the tab strip, the Classic tab is created at currentTab.index + 1, so it stays next to the Lightning tab you came from.
  • Home tab support — Lightning home and Setup now resolve to the Classic home and Classic Setup home consistently.
  • Dependency cleanup — pruned the lockfile and updated the toolchain.

Fixed

  • Popup fixes — small popup and tab-targeting corrections.

Notes

  • Still Manifest V3 with tabs and webNavigation permissions.
  • The Chrome Web Store listing may serve 1.3 until 1.4 finishes review.

Install

Install from the Chrome Web Store.

Historical release (February 2025). Superseded by v1.4 — use that version.

v1.2.0

Choose a tag to compare

@RIJUDEVx RIJUDEVx released this 06 Nov 11:53
e9b927f

Switch to Classic v1.2.0 — Faster, cleaner popup

A maintenance release focused on performance and popup reliability.

Changed

  • Content script rewrite — one header lookup per run instead of repeated querySelector calls, optional chaining, and less duplicated DOM work.
  • Service worker cleanup — tidier routing and tab handling.
  • Smaller build — webpack config trimmed and output reduced.
  • Version metadata — manifest and package metadata aligned on 1.2.

Fixed

  • Popup — the popup now reliably targets the active tab (dedicated tab-id provider and bootstrap), so the switch button acts on the page you are looking at.

Install

Install from the Chrome Web Store.

Historical release (2023–2024). Superseded by v1.4 — use that version.

v1.1.0

Choose a tag to compare

@RIJUDEVx RIJUDEVx released this 06 Nov 11:53

Switch to Classic v1.1.0 — Custom objects and reliable switching

The first round of real-world fixes after launch, driven by orgs with custom objects and Setup-heavy workflows.

Added

  • Custom object support — records on any object now resolve by their 15- or 18-character ID, not just standard objects.
  • Setup redirect — Lightning Setup (/lightning/setup/SetupOneHome/home) now opens the Classic Setup home instead of a record page.

Fixed

  • Switching back and forth — tightened the switcher timing so going Lightning → Classic → Lightning no longer lands on the wrong page.
  • Header placement — the button is inserted as a list item in the global header, so it survives layouts that broke on custom-object pages.
  • URL parsing and quoting — corrected org-domain extraction (.lightning.force.com vs /lightning path handling) and quote/encoding errors that could send you to the wrong host.
  • Popup UI — layout, styling, and icon fixes; the extension now uses the button_128.png mark.

Install

Install from the Chrome Web Store.

Historical release (March 2022). Superseded by v1.4 — use that version.

v1.0.0

Choose a tag to compare

@RIJUDEVx RIJUDEVx released this 06 Nov 11:53

Switch to Classic v1.0.0 — Initial release

The first public version of the extension: a one-click escape hatch from Salesforce Lightning to Salesforce Classic.

What's in it

  • Header button — “Switch to Classic Experience” is added to the Lightning global header, next to the profile menu.
  • Toolbar popup — the same action from the extension popup, so it works even when the header is not rendered.
  • Opens the same record — the current Lightning record's 15- or 18-character Salesforce ID is reused to open that record in Classic.
  • Home and Setup — Lightning home opens the Classic home.
  • Manifest V3 — Angular popup, webpack-built content script and service worker.

Install

Install from the Chrome Web Store, or see the current release for a packaged build.

Historical release (February 2022). Superseded by v1.4 — use that version.