Skip to content

CW-3261 - Nitro Sign corrupts files created/produced by Aspose#185

Merged
rlasskiy merged 1 commit into
mainfrom
rlasskiy/CW-3261
Feb 25, 2026
Merged

CW-3261 - Nitro Sign corrupts files created/produced by Aspose#185
rlasskiy merged 1 commit into
mainfrom
rlasskiy/CW-3261

Conversation

@rlasskiy

Copy link
Copy Markdown
Contributor

No description provided.

@rlasskiy rlasskiy merged commit 9d56656 into main Feb 25, 2026
1 of 3 checks passed
@rlasskiy rlasskiy deleted the rlasskiy/CW-3261 branch February 25, 2026 12:43
rlasskiy added a commit to Nitro/lazyraster that referenced this pull request Feb 25, 2026
# 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@latest`
  -  Nitro/lazypdf#185
- `go mod tidy`
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.

2 participants