Hi all,
I ran into a nav alignment bug and wanted to share it here in case it helps others (or the Bricks team) — full disclosure, I used Claude to help investigate and diagnose this, as I don’t have deep CSS knowledge myself, but the technical findings below were verified by inspecting the live computed CSS on my site. I’ve copied and pasted the Claude issue breakdown below.
The issue:
On the Nestable Nav Menu element, when you set a custom font-size under Item Typography, plain nav items (e.g. Home, About) and dropdown/toggle items (e.g. a “Collections” item with sub-items) end up different heights, causing the dropdown item to sit visibly higher or lower than the rest of the nav row.
Root cause:
Bricks renders the two item types with different display values:
- Plain items:
<li>with defaultdisplay: list-item - Dropdown/toggle items:
<li>withdisplay: flex
The Item Typography font-size setting only outputs CSS onto the <a> tag (and the toggle’s inner children) — it’s never applied to the <li> wrapper itself.
For the display: flex dropdown <li>, this doesn’t matter, because flex sizes the box to its actual content.
For the display: list-item plain <li>, though, the browser calculates that box’s line-height from the <li>'s own font-size — not the smaller font-size that’s only been applied to the <a> inside it. So the plain item’s <li> stays sized to the old/ambient font-size regardless of what you set in Item Typography, while the dropdown item’s <li> correctly shrinks — creating a height mismatch and vertical misalignment between the two.
The fix I applied (scoped to my specific nav element’s ID, via the element’s CSS panel):
css
#brxe-qiivpg .brx-nav-nested-items > li {
font-size: var(--text-s);
}
This forces the font-size onto the <li> itself (not just the <a>/toggle content inside it), so both item types compute their line-box height from the same value and end up the same height.
Expected behavior: setting one Item Typography font-size for the nav should produce consistent <li> heights across all item types, plain or dropdown. Right now that’s only true if you also manually patch the <li> font-size yourself.
I’ll share a link to a test page below so you can see it live. Let me know if this is a known issue or if I should file it separately.
**
Browser**: Chrome 152
OS: macOS
URL: Test - Michael Wake Photography
Video: Short screen recording that illustrates this issue (free tool: jam.dev)
[Please describe this bug in as much detail as possible so we can replicate & debug this bug]