Navigation overflow trigger chevron renders below the label instead of inline

Open
#4,629 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@chubes4 is already working on this.

Since Nov 6, 2026.

  • #4635 by @chubes4 — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
css, html, php
Domain
frontend

Research direction

Start by tracing how the imported navigation trigger handles a label followed by an inline SVG chevron, then locate the contract or visual parity tests for imported headers. Compare the rendered trigger geometry with the source at desktop width; done means the chevron stays inline and vertically centered, with the trigger height and underline matching the source.

Written by the indexing model from the issue text.

Description

Summary

A navigation overflow/submenu trigger whose label is followed by an inline chevron icon renders the chevron as a caret below the label instead of inline after it.

Observed

Source renders More ⌄ with the chevron inline, vertically centred with the label. The imported header renders "More" with the caret under the text, so the trigger height and underline position change. Seen both in the shared header part and on routes that keep their own header.

Acceptance

  • An overflow trigger built from label + inline svg chevron keeps the chevron inline after the label, matching the source box geometry at desktop width.
  • Contract or visual-parity test covers the label+chevron trigger shape.

AI assistance: filed by Claude (Claude Code via Roadie) while investigating a site-builder capture import; findings verified against a private local fixture and rendered output.

Dominant language
PHP
Stars
25
Forks
3
Avg merge
3h 25m
Merged PRs (30d)
935

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/blocks-engine

All issues in Automattic/blocks-engine

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.