zen-browser/desktop

"Close Pinned Tab Shortcut Behavior" ignored for "Places" tab

Open

#12353 opened on Feb 13, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (42,031 stars) (1,498 forks)batch import
Bugcomponent: tabsgood first issueplatform: windows

Description

Preliminary Checks

  • I have read and understood the important section above.
  • I have searched existing issues and avoided creating duplicates.
  • I am not filing an enhancement request.
  • I have checked that this issue cannot be reproduced on Mozilla Firefox.
  • I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS.

What happened?

Hi! This is a rare case, I believe. I'm using the chrome://browser/content/places/places.xhtml tab to have a dedicated full-window history tab, because I find Sidebar History hard to use and navigate. I accidentally closed this tab, and found it out way later - so I had to reopen it again (and as I don't recall this entire URI, I had to find it again). I found that there's a "Close Tab Shortcut Behavior" setting, which I thought would help me prevent this from happening again. I tinkered with it, with no result. Just when I wanted to forget about this option, I tried it on the 2nd essential tab, with "regular page" opened there, and the tab didn't close, as per "Switch to next tab" behavior, set in the Settings. It acts the same way when the tab is pinned, not added to the Essentials.

OS: Windows 10

Expected behavior

On the essential/pinned tab closing, the configured behavior is executed, like for the "regular page" tabs

Actual behavior

The page is closed regardless of the "Close Tab Shortcut Behavior" configuration

Steps to reproduce

Steps:

  1. Set "Close Tab Shortcut Behavior" to "Switch To next tab".
  2. Open chrome://browser/content/places/places.xhtml.
  3. "Pin Tab" or "Add to Essentials".
  4. Open this tab.
  5. Press Ctrl+W.

Screenshots and videos

Image

Version

1.18.5b

What platform are you seeing the problem on?

Windows - x64

What component is this issue related to?

Tabs

Contributor guide

Tech stack
javascript
Domain
desktopfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScript knowledgeUnderstanding of browser tab events
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Investigate the implementation of the 'Close Tab Shortcut Behavior' setting in the tab management code. Look for conditional logic that handles the 'places' tab separately, possibly in the tab closing event handler. Check if the setting is being overridden for internal pages like chrome:// URLs. Consider testing with other internal tabs to see if the bug is isolated to the places tab.