Repository navigation
Keep WebMCP reminders in content flow and preserve footer controls - #239
Merged
Merged
Conversation
chen21019
force-pushed
the
fix/webmcp-pending-review-layout-20261101
branch
from
November 1, 2026 05:39
eba611e to
d97a899
Compare
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
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.
The pending-plan reminder rendered after the authenticated footer could intercept normal clicks on language and CLI controls. Mount the same explicitly gated review component once in authenticated main content; retain its review observer, global modal and manual-consent behavior. Scope wrapping and existing theme tokens to the reminder so long target paths, translated controls, RTL and narrow viewports remain usable.
Validation: the directly affected collaboration entry passed 35 cases once. One new QUnit regression exercises 96 width/direction/theme/copy/path combinations with actual emitted theme/vendor CSS and current scoped Sass in a single local browser. Two-theme normal/hover/keyboard-focus samples pass contrast checks; all three templates parse. These are isolated source/layout results, not the outstanding published/native workflow PASS. The earlier qualified 27ba candidate remains preserved and unpublished; fresh full/enabled producer, CodeQL, original artifact/SBOM/attestation qualification and QA8080 workflows are required. No session/auth/API/dependency changes or production access; versions 1.6.203/bridge0.2.5 remain unpublished and their tags have not been created.