Repository navigation
organize: split a combined field/widget so every copied page owns its widget - #2289
Open
midasmatterhorn wants to merge 1 commit into
Open
midasmatterhorn wants to merge 1 commit into
midasmatterhorn wants to merge 1 commit into
Conversation
midasmatterhorn
force-pushed
the
fix/issue-1810-split-field-widget
branch
from
October 16, 2026 12:09
a7b18d7 to
4f0493c
Compare
This branch has not been deployed
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.
A widget that doubles as its own field (
/Subtype /Widget, no/Parent) was copied once and shared between both copies of a repeated page, so only the last page could identify it (its/P) and per-page annotation edits were impossible. Page import now splits such a widget into a parent field holding the field keys (name, value, flags) and a widget child holding the annotation keys (rectangle, appearance, page), registers the parent in/AcroForm /Fields, and gives every later copy of the page its own widget child in the parent's/Kids. The repeated-page independence test no longer exempts own-field widgets, and a new test requires distinct widgets, correct/Pper page, and one shared parent/value after save and reopen.Fixes #1810