Repository navigation
Place the API spec menu below its trigger - #4280
Merged
Merged
Conversation
The open travel was tuned for a tall tab, so the spec menu covered its label and painted under the header and sidebar. Co-Authored-By: Grok 4.7 <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Docs preview (local build)Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/4280/ |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Approved — no blocking issues found.
What is this? | From workflow: PR Review
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Member
Author
|
LGTM 
|
reakaleek
marked this pull request as draft
October 1, 2026 11:53
reakaleek
marked this pull request as ready for review
October 5, 2026 08:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assembler preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/4280/api/doc/cloud-connect
The API spec menu opens below the control that opened it, and it paints above the left nav and the page header.
Affects: Site UI, API reference
Prompt summary: Position the API spec-chooser flyout so the trigger stays visible, the menu stacks above the left nav and the page header, and Escape closes it and returns focus to the trigger.
Why
The spec menu shares its open travel with the tall top-bar tabs. That travel moves the panel up by 8px. The spec control is only as tall as its label, so the panel covers the bottom of the label. The panel's z-index also sits inside the grey bar, so the page header and the API sidebar paint over the menu.
Closes elastic/docs-eng-team#901
What
Spec menu placement
The spec menu and the download menu start below the label. After the open travel, the panel sits 4px under the control, so the label stays fully visible.
Stacking
While either menu is open, the grey bar paints above the API sidebar and the page header. Escape already closes these menus and returns focus to the trigger. That behavior is unchanged.
Verify
Open an API product page and open the spec menu. The label stays visible. The panel sits above the left nav and the page header. Escape closes the menu and focus returns to the label.
Out of scope. This PR does not add catalog display names, and it does not change property-tree chips, the examples panel, or
OperationPageModel.Made with Cursor