2058718 - [Nova] Sidebar / content is inconsistent with chrome / content gap

Status: RESOLVED FIXED

(Firefox :: Sidebar, defect, P2)

Description

[Nika Layzell [:nika] (ni? for response)]

Attachment: Screenshot 2026-07-28 at 5.57.45 PM.png

It appears that the --chrome-window-gap is not being applied consistently on the gap between the primary content and the sidebar. The gap appears visually to be ~twice as large as other gaps (e.g. the gap between the toolbar & web content, or the gap between the sidebar and the window border).

I think it's not quite twice as wide, but perhaps ~2px too wide? Perhaps borders aren't being compensated for?

---

STR: Open a browser window with Nova enabled, and open the sidebar.

ER: The sidebar gap appears consistent with other gaps

AR: The sidebar gap is approximately 2px wider than other gaps.

Comment 1

[Nika Layzell [:nika] (ni? for response)]

Attachment: Screenshot 2026-07-28 at 6.47.09 PM.png

FYI, It appears this extra gap also appears in compact mode. I've attached a screenshot of that as well. I'm vaguely guessing that this has the same cause.

Comment 2

[Ania]

Thank you for the report, Nika!
We'll address it in both modes, however, in the standard / automatic mode, it's the gap between chrome and content that is not up to spec. Both should be 4 px (image attached).

Comment 3

[Ania]

Attachment: gaps.png

Comment 4

[Nika Layzell [:nika] (ni? for response)]

Attachment: Window creation gap inconsistency

One other thing I recently noticed, which might be related here, or might be a different bug, is that the spacing between the vertical tab strip and the main content appears to vary depending on whether the window was created already within compact mode, or after toggling from normal mode to compact mode while the browser is running.

e.g. if the window is started in compact mode, there is almost no gap (it looks like the two things are overlapping). If you then toggle to non-compact mode, the objects remain overlapping. I've attached a picture which hopefully should explain what I mean here.

It seems like perhaps some part of this spacing is "sticky" and specified when the window was created, rather than being dynamically dependent on the current state of the window?

Comment 5

[Nika Layzell [:nika] (ni? for response)]

Given the recent changes in bug 2063294, there are no longer gaps which need to match. GIven that, I don't think this is a valid bug anymore, and can be closed.