Plugin’s admin framework CSS leaks a 3px green top border
-
Since updating to WordPress 7.0.1, every post/page editing screen showed an unexplained 3px solid green border (rgb(67, 126, 71)) running across the very top of the editor canvas. It was present on published posts, drafts, and pending review posts alike, and only inside the post editor — not on the front end, and not on any other admin screen.
Root cause (confirmed via DevTools):
The rule is coming from this plugin, from:
https://[mysite]/wp-content/plugins/searchwp-live-ajax-search/assets/styles/admin/framework/style.css?ver=1.0.0Specifically:
body {
border-top: 3px solid rgb(67, 126, 71);
…
}This selector targets the bare
bodyelement with no scoping to the plugin’s own admin/settings wrapper. Disabling the plugin makes the border disappear immediately, confirming the source.Why this only surfaced now (WP 7.0):
This rule has likely been shipping in the plugin for a while, but it was invisible before WordPress 7.0 because:
- It appears to be enqueued via a hook that also loads on the post editor screen (e.g.
enqueue_block_editor_assets), not just the plugin’s own settings page. - Prior to WP 7.0, the post editor was not consistently rendered inside an isolated iframe, so the real wp-admin
<body>was used — and the fixed admin toolbar at the top of the screen covered that 3px border, making it invisible. - WordPress 7.0 now enforces an iframed editor canvas whenever all blocks in a post use Block API v3+ (see: https://make.wordpress.org/core/2026/02/24/iframed-editor-changes-in-wordpress-7-0/). The iframe’s own
<body>has no admin toolbar covering it, so this previously-hidden border is now fully exposed at the top of the editing canvas.
Suggested fix:
Scope the selector in admin/framework/style.css to the plugin’s own settings page wrapper (e.g. a specific class/ID on the settings container) instead of the bare
bodyelement. That should prevent any styles from this framework stylesheet leaking into other contexts, including the block editor iframe going forward, and likely other places this stylesheet gets enqueued.Environment:
- WordPress 7.0.1
- SearchWP Live Ajax Search 1.8.7
- Reproducible on any post/page editor screen, across browsers (confirmed in Firefox and Vivaldi, including private/incognito windows with extensions disabled, ruling out a browser extension)
Happy to provide screenshots, a screen recording, or further debugging details if useful. Thanks!
- It appears to be enqueued via a hook that also loads on the post editor screen (e.g.
You must be logged in to reply to this topic.