Repository navigation
Releases
Release v2.6.0
v2.6.0 — Improved Bookmark Editing Compatibility
This release fixes a bookmark URL-rewriting race condition that could prevent Chrome’s “Choose another folder” editor from opening or interfere with saving bookmark names and folder changes.
What's Improved
- Safer bookmark editing: URL changes are deferred while a matching page remains selected in any Chrome window.
- More reliable recovery: Pending bookmark updates survive background-worker restarts, browser restarts, and extension reloads.
- Better handling of concurrent changes: Older pending operations cannot overwrite newer edits or reapply markers after processing has been paused.
- Less background work: Bookmark updates share a single timer, storage writes are batched, and deferred work waits for browser events instead of periodic polling.
- Expanded regression coverage: Added 31 bookmark tests, bringing the total to 57 passing tests.
Important Note
Newly saved bookmarks or bookmarks with edited URLs may temporarily retain Chrome’s default opening behavior. To allow the extension to apply its URL marking:
- Switch tabs, navigate away, or close the matching page.
- Allow approximately 5 seconds for marking to complete.
Note: Closing the bookmark dialog alone may leave marking deferred.
Verification
- ✅ Automated tests passed
- ✅ Source checks passed
- ✅ Build checks passed
- ✅ ZIP verification passed
- ⏳ Native Chrome dialog verification is still pending
Release v2.5.0
Download-free bookmark opening
v2.5.0 replaces the dummy-download mechanism with a local HTTP 204 No Content response. The extension no longer starts an empty.zip download and races to cancel it before Chrome shows a Save As dialog or download animation.
The reporter has confirmed that the new mechanism resolves their macOS Chrome download-popup issue.
What changed
- Removed dummy downloads. Marked bookmark navigations now receive a bodyless, HTML-typed 204 response from the extension's service worker. No ZIP download, download-history erasure, or global download-UI suppression is involved.
- Reduced permissions. Removed
downloadsandalarms, along with the periodic keep-alive alarm. No new permissions were added. - Simplified tab handling. Removed the second, download-driven tab opener. Navigation handoffs are tracked by source tab, and native newly opened bookmark tabs can be reused instead of relying on Chrome's download-related tab cleanup.
- Safer fallback behavior. Later navigations and tab removal invalidate old handoffs. If history restoration fails, the extension no longer closes the existing source tab.
- Preserved compatibility. Existing bookmark markers, Gmail/Outlook wrappers, pause-time restoration, focus/placement settings, and the bookmark-editing delay remain in place.
Project maintenance
- Split the background worker into focused scripts with synchronous loading.
- Removed obsolete distribution archives, duplicate guidance, and outdated release notes.
- Added dependency-free validation/build tooling and a runtime-only package boundary.
- Updated the README, architecture/testing documentation, and privacy descriptions.
Verification
- All 26 automated regression and packaging tests pass.
- The attached ZIP contains 17 runtime files, with
manifest.jsonat its root. ZIP integrity and byte-for-byte comparisons against the release target passed. - The reported macOS download-popup fix is user-confirmed. Automated tests do not establish complete cross-platform, cold-start, incognito, or media-playback compatibility; those browser checks remain important before publication.
Known limitations
- A 204 can preserve the source document but may still trigger page lifecycle handlers. Uninterrupted Spotify or other streaming playback is not guaranteed. If affected, pause the extension and use Cmd/Ctrl-click or middle-click.
- Special-domain bookmarks still use the existing hosted wrapper and may show its favicon. If the helper loads as a fallback, its request includes the encoded destination URL.
- Non-HTTP(S) bookmarks retain native browser behavior. Newly created bookmarks remain unmarked briefly while editing settles.
- Pause in the extension popup before disabling or uninstalling to restore bookmark URLs.
Download and upgrade
Use Open-Bookmarks-in-New-Tab-v2.5.0.zip from the release assets. For manual testing, extract it and use Load unpacked in a separate Chrome profile; do not run it alongside the store version against the same bookmarks.
Existing bookmark formats are retained; no manual bookmark conversion is required. Chrome Web Store publication is separate from this GitHub release.
Release v2.4.0
v2.4.0 — Duplicate tabs, disappearing tabs, and bookmark renaming
This release is almost entirely bug fixes, focused on one family of problems: clicking a
bookmark could open two tabs, or make tabs disappear. Several long-standing reports
turned out to share a single root cause.
If you use this extension daily, this is the release to update to.
Fixed — duplicate and disappearing tabs
- Clicking one bookmark opened two identical tabs. Most visible with Focus new tab
turned off, which is why some users saw it constantly and others never did. The setting
was never the cause — it was only hiding the bug. - "Open all bookmarks" left only one tab open, with the rest vanishing. All the
bookmarks in the folder were collapsing onto a single tab. - Cmd/Ctrl+click and middle-click opened a tab that immediately disappeared.
- Internal / LAN addresses (e.g.
192.168.x.x, router admin pages) opened two copies. - Gmail and Outlook bookmarks opened two tabs.
Fixed — bookmarks
- Renaming a bookmark while saving it no longer gets lost. Previously, pressing
Ctrl/Cmd+D and changing the name in the save popup would silently keep the original
name. Renaming afterwards via right-click → Edit worked, which made the bug look random. - Gmail / Outlook bookmarks saved by older versions now convert automatically. Before,
updating the extension left them in their old, broken form — the only way to fix them was
to manually pause and re-enable the extension. Bookmarks now migrate on update, in both
directions, whenever the special-domain list changes. - Bookmarks added while the extension was paused are no longer modified. Adding a
bookmark shortly after pausing could still rewrite its URL.
Fixed — reliability
- The extension could silently stop working after being paused once. Its on/off setting
and its redirect rule could drift out of agreement — the extension looked enabled but
behaved completely differently. They are now checked and reconciled every time the
extension starts. - Real downloads are no longer cancelled by mistake. In rare cases a genuine file
download could be claimed and cancelled by the extension. - New tabs open in the correct window in multi-window setups, and respect the chosen
position more reliably. - Rapid consecutive bookmark clicks no longer confuse the extension's internal state.
Security
- The redirect helper page now only follows
http(s)destinations. This page is used
for Gmail/Outlook bookmarks and takes its destination from the URL. A hand-edited or
synced bookmark could previously point it at ajavascript:URL, which would run in the
page's origin. The destination is now validated before it is used or shown as a link.
Behaviour changes worth knowing
- A newly created bookmark is now activated a few seconds after you finish editing it.
This is what makes renaming-while-saving work. During those few seconds the bookmark opens
in the current tab rather than a new one. This is intentional. - Cmd/Ctrl+click and middle-click now keep the new tab in the background, matching
Chrome's normal behaviour, instead of following the Focus new tab setting.
Known issues
These are not fixed in this release:
- A bookmark tab that is still loading can be closed if you click another bookmark before
its page has loaded. If the tab still shows Untitled / Loading with no title or
favicon, clicking a second bookmark may discard it. Waiting until the page title appears
avoids it. A fix is in progress. - A brief
empty.zipdownload may still appear on some systems. It is a dummy file used
to stop the current page from navigating, and it is cancelled automatically — but it can
flash in the download bar before that happens. - Media on the current page can still be interrupted when a bookmark is clicked. Spotify
Web Player is the most reliable example. This is a Chrome extension platform limitation. - Uninstalling while the extension is enabled leaves the
newtab@prefix in your bookmark
URLs. Chrome gives extensions no chance to clean up on uninstall. Pause the extension
first, which restores every bookmark, and then uninstall.
Upgrading
No action needed — just update. Existing bookmarks are migrated automatically the first time
the new version runs.
If you previously worked around the Gmail/Outlook problem by pausing and re-enabling the
extension, you no longer need to.
v2.3.0
What's New in v2.3.0
A small patch release fixing two bugs reported after v2.2.0.
🐛 Fixed: ChatGPT bookmark closing itself when opened from a new tab page
When the current page was Chrome's default new tab page, clicking the ChatGPT bookmark (or any bookmark whose destination performs a server-side redirect) caused the bookmark to load briefly and then the tab to close itself.
Root cause: The extension reuses empty new-tab pages to load the bookmark directly (single-tab UX). But onCommitted later fired with the post-redirect URL (e.g. chat.openai.com → chatgpt.com), which no longer matched the original URL the extension was tracking. The mismatch triggered a "restore" code path that closed the tab.
Fix: Replaced the fragile URL comparison with an explicit reused flag. When the extension reuses the source tab, that flag is set and onCommitted now skips the restore logic entirely — independent of any redirects the destination site performs.
🐛 Fixed: baidu.com covering the tab on the left in Microsoft Edge
A user reported that opening a baidu.com bookmark in Microsoft Edge would also navigate the left-adjacent tab to baidu.com, effectively replacing two tabs at once.
Fix: Added baidu.com to the CREDENTIAL_STRIPPED_DOMAINS list, so Baidu bookmarks are now wrapped through the GitHub Pages redirect proxy (same mechanism used for Gmail/Outlook). This avoids Edge's credential-stripping behavior on the baidu.com domain and stops the cross-tab navigation.
Files Changed
js/background.js—reusedflag tracking inhandledTabs, refactoredopenInNewTabto accept source tab ID, addedbaidu.comto credential-stripped domainsmanifest.json— version bump to 2.3.0
v2.2.0
What's New in v2.2.0
🔧 Fixed: Download UI flash when opening bookmarks
When opening a bookmark for the first time (especially after Chrome restarted), a download window would briefly flash before disappearing. This happened because the service worker wasn't awake fast enough to cancel the empty.zip download.
Fix: Added chrome.webNavigation.onBeforeNavigate as a primary interceptor that fires before the download is even created. The new tab opens immediately, and the download is suppressed with chrome.downloads.setUiOptions. The download listener remains as a backup.
🌐 Fixed: Gmail & Outlook bookmarks not working
Bookmarks to Gmail (mail.google.com) and Outlook (outlook.live.com, outlook.office.com, etc.) silently failed — Chrome's network stack strips the newtab@ userinfo from these high-security HSTS preload domains before declarativeNetRequest can match the URL.
Fix: Bookmarks pointing to these domains are now wrapped through a redirect page proxy hosted on GitHub Pages. The newtab@ prefix is applied to the proxy domain instead, which Chrome does not strip. The extension's redirect rule intercepts it normally, and the real URL is opened in a new tab.
🔄 Fixed: Settings not syncing across devices
The on/off toggle and other settings were stored in chrome.storage.local, meaning each device had independent settings.
Fix: Migrated all settings and language preference storage from chrome.storage.local to chrome.storage.sync. Changes now propagate across all signed-in Chrome instances automatically.
🆕 New: Fallback landing page
When a redirect-page bookmark is opened with the extension disabled or uninstalled, users now see a branded landing page (instead of a broken URL) with:
- Auto-redirect to the intended bookmark destination
- Chrome Web Store install link
- Feature overview and how-it-works guide
📝 Updated: Known Limitations in README
- Documented the media playback interruption issue on streaming pages (Spotify, YouTube) as a fundamental MV3 platform limitation, with Ctrl+Click / middle-click workaround
- Documented missing favicons for Gmail/Outlook bookmarks due to redirect page proxy
Files Changed
js/background.js— Redirect page proxy, credential-stripped domain handling, storage.sync migration, enhanced webNavigation fallbackjs/popup.js— storage.sync migration for language preferencedocs/redirect.html— New fallback/landing page for redirect-page bookmarksREADME.md— Updated known limitations section
v2.1.0
The first official version of the extension.