CW-3261 - Nitro Sign corrupts files created/produced by Aspose#401
Merged
Conversation
rlasskiy
changed the title
Prabhsimar25
approved these changes
Feb 25, 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
2 participants
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.
Links
https://gonitro.atlassian.net/browse/CW-3261
#401
Description
When we add a /Resources dictionary directly to a page (Root/Pages/Kids/[0]/Kids/[0]/Resources), the page stops inheriting resources from its parent /Pages node.
In PDF, /Resources is an inheritable entry in the page tree. If a page does not define /Resources, it resolves them by walking up the parent chain. However, once we explicitly set /Resources on the page, inheritance stops completely. The page will only use the resources defined in its own dictionary.
Currently, when we add a page-level /Resources, we do not merge in the inherited parent resources (Fonts, XObjects, ExtGState, etc.). As a result, resources that were previously available via inheritance become undefined, which can break rendering
To avoid this, we replicate Nitro Pro behavior and reuse the parent /Resources, ensuring that existing inherited resources remain available.
Key changes
go get github.com/nitro/lazypdf/v2@latestgo mod tidy