Add Designer/runtime layout parity test suite - #92
Merged
ProGraMajster merged 1 commit intoAug 20, 2026
Conversation
- compare Designer layout against real runtime layout semantics - cover Dock, Anchor, Padding, nested containers and UserControl roots - add serialization/codegen and reverse-parser parity regressions - provide deterministic diagnostics for layout mismatches - document and centralize Designer/runtime parity coverage
ProGraMajster
deleted the
codex/issue-42-designer-runtime-layout-parity
branch
August 20, 2026 18:35
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.
Summary
Adds a deterministic, headless Designer/runtime layout parity harness. It builds equivalent trees and compares actual
DesignerLayoutEnginegeometry with real ModernFormsNext controls laid out through the production runtimeControl.PerformLayoutpath. The harness records normalized structured snapshots and emits scenario, control path, property, runtime value, and Designer value for every mismatch; it does not contain a second Dock/Anchor/Padding algorithm.Coverage
.mfdesignsave/reopen serializationBugs found and fixed
Sizeinstead of semanticClientSizeScrollableControlcould reinitialize Anchor data during a bounds-driven resize before runtime layout consumed itRegression coverage
Validation
git diff --check: cleanThe parity suite is deterministic and headless: no flaky retry mechanism, no
Thread.Sleep, no monitor-derived DPI dependency, and no visible-window requirement.Follow-ups
Closes #42