fix(codec): keep Browser auto-layout variance evidence-only - #701
Merged
Merged
Conversation
SunSi12138
deleted the
fix/browser-autolayout-evidence-only-20260918
branch
September 18, 2026 10:34
SunSi12138
added a commit
that referenced
this pull request
Sep 18, 2026
Advance the main synchronization branch to the current dev tree after #701. Keep the known unsupported Browser auto-layout variance as retained evidence without making it a release blocker.
This was referenced Sep 18, 2026
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.
Refs #387.
Browser/wasm32 currently runs Mono while hosted desktop runs CoreCLR/64-bit. The retained
auto-layout-release-scopedfixtures intentionally exerciseLayoutKind.Autoand framework-owned nested layouts whose raw managed representation is not a supported cross-runtime ABI contract.This change keeps those Browser <-> hosted-desktop mismatches in the retained compatibility evidence but makes only their recognized layout/decode mismatch classifications non-blocking. The validator still checks the exact failure shape.
Still blocking:
auto-layout-release-scoped;No production codec hot-path change and no broad
continue-on-error/retry/timeout weakening.