Skip to content

ref(navigation): Hide page-level FeedbackButtons when page-frame is enabled#111826

Draft
JonasBa wants to merge 1 commit intomasterfrom
jb/pageframe/feedback
Draft

ref(navigation): Hide page-level FeedbackButtons when page-frame is enabled#111826
JonasBa wants to merge 1 commit intomasterfrom
jb/pageframe/feedback

Conversation

@JonasBa
Copy link
Copy Markdown
Member

@JonasBa JonasBa commented Mar 30, 2026

Hide per-page FeedbackButton instances when the page-frame feature flag is enabled.

The TopBar (views/navigation/topBar.tsx) now renders a global FeedbackButton for all pages under the page-frame feature. Having individual feedback buttons on every page header alongside the TopBar one results in duplicates.

This adds a useHasPageFrameFeature() check to all 39 page-level usages so they return/render nothing when the flag is on. Usages inside modals and overlays (command palette, replay comparison modal, search filter dropdown) are intentionally left unchanged since the TopBar is not visible in those contexts.

Wrapper components (AutofixFeedback, AutomationFeedbackButton, MonitorFeedbackButton, DynamicAlertsFeedbackButton) use an early return null. Direct page-level usages gate the JSX with {!hasPageFrame && <FeedbackButton />}.

…nabled

The TopBar now renders a global FeedbackButton for all pages when the
page-frame feature is enabled. Hide the per-page FeedbackButton
instances to avoid duplicates, while keeping usages inside modals and
overlays unchanged.

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant