Skip to content

feat(explorer): updated drawer header with dropdown menu#113637

Merged
aliu39 merged 12 commits into
masterfrom
aliu/menu-update2
Apr 22, 2026
Merged

feat(explorer): updated drawer header with dropdown menu#113637
aliu39 merged 12 commits into
masterfrom
aliu/menu-update2

Conversation

@aliu39

@aliu39 aliu39 commented Apr 22, 2026

Copy link
Copy Markdown
Member
  • update topbar to match new designs
  • migrate session history from the custom floating menu to an ellipses dropdown, achieved w/a item-level closeOnSelect=false
  • don't support /resume slash command for now as it'll need to integrate w/the dropdown (can do in followup, but low prio)

(CE CM toggles are internal-only)

menu.mov

@aliu39
aliu39 requested review from a team as code owners April 22, 2026 05:03
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 22, 2026
Comment thread static/app/views/seerExplorer/components/explorerMenu.tsx
Comment thread static/app/views/seerExplorer/components/drawer/explorerDrawerHeader.tsx Outdated
@aliu39 aliu39 changed the title feat(explorer): updated drawer header with dropdown actions feat(explorer): updated drawer header with dropdown menu Apr 22, 2026

@Zylphrex Zylphrex left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few questions but otherwise LGTM

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More of a general design question - Any reason why we chose to hide the close button text instead of keeping it consistent everywhere?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was matching the figma - personally I think it looks cleaner, but don't have a strong preference

* Whether to close the menu when this item is clicked. Overrides the list-level
* `closeOnSelect` prop when set.
*/
closeOnSelect?: boolean;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this override necessary when we can just set the closeOnSelect on the item?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the item-level closeOnSelect wasn't available before, only an option for closeOnSelect on all items. For all items except history, we want to close on select

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 7cd4921. Configure here.

@aliu39
aliu39 enabled auto-merge (squash) April 22, 2026 16:16
@aliu39
aliu39 merged commit f81ab73 into master Apr 22, 2026
64 of 65 checks passed
@aliu39
aliu39 deleted the aliu/menu-update2 branch April 22, 2026 16:20
@github-actions github-actions Bot locked and limited conversation to collaborators May 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants