Preserve identified form visual parts and responsive CSS facts - #1647
Merged
Conversation
…isual-payload # Conflicts: # php-transformer/tools/visual-parity/package.json
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
1 participant
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.
Purpose
Tracked by #1638. Preserve source-owned visual content and layout custom-property facts when forms are reduced to a provider-neutral WordPress site plan.
Changes
trunk, retaining the upstream button-height visual regression alongside the form empty-group regression.Evidence
composer validate --strictand the fullcomposer testsuite passed, including 307 parity fixtures and package-install proof.npm testinphp-transformer/tools/visual-paritypassed, including empty-group editor-height and button-height ownership browser checks.Draft Gate
This is not a solved-site claim. Canonical fresh import verification has not run, so frontend and editor parity remain pending coordinated verification with #1579. The local WordPress materialization integration was not run because it writes to the installed test runtime.
AI assistance: GPT-6 Astra through OpenCode was used for merge-conflict resolution, test orchestration, and PR evidence refresh.