Skip to content

Fix bug in patch merge candidate selection. - #283

Merged
garretrieger merged 1 commit into
w3c:mainfrom
garretrieger:patch_merge_fix
Nov 9, 2026
Merged

garretrieger merged 1 commit into
w3c:mainfrom
garretrieger:patch_merge_fix

Conversation

@garretrieger

Copy link
Copy Markdown
Contributor

ComputeCandidatePatchMergeGlyphs() was being run on merge init. It aims to record all glyphs belonging to non-exclusive patches as candidates for patch merging. However, merges after the initial setup can move some of those glyphs into exclusive patches, which in turn leads to patch merge evaluation against exclusive patches. This moves candidate glyph computation to after segment merging is complete and further filters out exclusive conditions during merge evaluation.

ComputeCandidatePatchMergeGlyphs() was being run on merge init. It aims to record all glyphs belonging to non-exclusive patches as candidates for patch merging. However, merges after the initial setup can move some of those glyphs into exclusive patches, which in turn leads to patch merge evaluation against exclusive patches. This moves candidate glyph computation to after segment merging is complete and further filters out exclusive conditions during merge evaluation.
@garretrieger
garretrieger merged commit c0ed516 into w3c:main Nov 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant