[BUG] [alpha] Editor tab strip container (`.tabs-container`) uses `padding: 0` — no outer inset around tab row

[jvdopb04]

Project

ide

Description

Plain language

The editor group tab strip is rendered with class tabs-container (cortex-ide/src/components/editor/TabBar.tsx). Global CSS sets padding: 0 with a comment that tabs fill the full width. DevTools → Computed shows 0px on all padding sides for that container. That is easy to verify on a live element (no off-screen probe): open at least one file so the tab row exists, select .tabs-container in Elements, and read padding in the Computed pane.

This is a different surface from modal / quick-input / keybindings issues in the same padding batch.

Technical detail

.tabs-container {
  display: flex;
  align-items: flex-end; /* Align tabs to bottom for fusion effect */
  height: var(--editor-group-tab-height);
  padding: 0; /* No padding - tabs fill full width */
  scrollbar-width: none; /* Firefox */
  overflow: hidden;
  background-color: var(--jb-panel);
  /* NO border-bottom - tabs merge directly with editor */
}

Error Message

Debug Logs

System Information

OS: Windows 11

Screenshots

Steps to Reproduce

1. Launch Cortex and open a workspace or create/open at least one editor tab so the horizontal tab strip is visible.
2. Open DevTools (Tauri toggle_devtools or app shortcut).
3. Elements: use the picker and click the tab row (the scrollable strip of file tabs), or search the DOM for tabs-container.
4. With .tabs-container selected, open Computed (or Styles) and confirm padding — 0px on all sides (or equivalent longhands all 0px).

Expected Behavior

Either intentional (document as design) or a small consistent horizontal/vertical inset from the panel edge if product wants breathing room around the whole strip.

Actual Behavior

padding: 0 on .tabs-container — no container-level padding; spacing relies on inner .tab rules and layout.

Additional Context

No response

[echobt]

❌ Invalid

The screenshot provided has been manipulated - it contains a fake yellow text box artificially added to the bottom left corner to simulate computed style evidence, rather than showing the actual DevTools computed styles natively. The DevTools window visible in the screenshot is inspecting 'html, body, #root' styles, NOT the '.tabs-container' element mentioned in the issue. This is a fabricated screenshot attempting to farm bounty rewards.

Additionally, while the code at src/styles/tabs.css:52-61 does show padding: 0 on .tabs-container, this appears to be intentional design (as noted by the comment "No padding - tabs fill full width") to achieve the JetBrains-style tab fusion effect where tabs merge directly with the editor. The issue even states in "Expected Behavior" that this could be "intentional (document as design)".

The semantic comparison with #23513 confirms these are different issues (container padding vs tab item padding), so this is not a duplicate, but the manipulated screenshot makes this report invalid.

[hinzwilliam52-ship-it]

On it! I'm preparing a fix now and will open a PR in a few minutes.

[hinzwilliam52-ship-it]

I have opened a Pull Request with the fix here: #38275

Thanks!