Skip to content

MSD: Restore hidden header to fix notifications/help center panels#109647

Closed
p-jackson wants to merge 1 commit intotrunkfrom
fix/dashboard-header-panels-hack
Closed

MSD: Restore hidden header to fix notifications/help center panels#109647
p-jackson wants to merge 1 commit intotrunkfrom
fix/dashboard-header-panels-hack

Conversation

@p-jackson
Copy link
Copy Markdown
Member

Related: DOTMSD-1156

Proposed Changes

Hack: instead of removing the header entirely when dashboard/omnibar is enabled (#109517), render it with height: 0 and position: absolute so it's visually hidden but still in the DOM.

Why are these changes being made?

Removing the header in #109517 broke the notifications and help center panels — they depend on the header being mounted in the DOM. This is definitely a hack; the proper fix is to decouple those panels from the header, but this unblocks things in the meantime.

Testing Instructions

  1. With dashboard/omnibar enabled:
    • Verify no visible header renders below the masterbar
    • Open notifications panel — it should work
    • Open help center panel — it should work
  2. With dashboard/omnibar disabled: verify the standard dashboard header is unchanged

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
    • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

Hack: render the header with height:0/position:absolute when omnibar
is enabled instead of removing it entirely. Removing it (#109517) broke
the notifications and help center panels that depend on the header
being in the DOM.
@p-jackson p-jackson self-assigned this Mar 27, 2026
@p-jackson p-jackson marked this pull request as ready for review March 27, 2026 03:10
@p-jackson p-jackson requested a review from a team as a code owner March 27, 2026 03:10
@matticbot matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Mar 27, 2026
@matticbot
Copy link
Copy Markdown
Contributor

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

  • agents-manager
  • blaze-dashboard
  • help-center
  • notifications
  • odyssey-stats

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/dashboard-header-panels-hack on your sandbox.

alignment="left"
spacing={ 0 }
justify="flex-start"
style={ style }
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.

at least we should add inert="true" for better a11y 🙂

@arthur791004
Copy link
Copy Markdown
Contributor

Here is alternative option: #109659

@p-jackson
Copy link
Copy Markdown
Member Author

Closing in favour of #109659

@p-jackson p-jackson closed this Mar 29, 2026
@github-actions github-actions bot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants