Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.1.3
-
Fix Version/s: 6.2.1
-
Component/s: Core/Parsing, Core/Rendering
-
Labels:None
-
Environment:any
-
Support Case References:Support Case #14004 - https://icesoft.my.salesforce.com/5007000001hEwzC
Description
A customer has submitted a PDF that contains two button annotation types that are not drawn on the screen. Further investigation is needed.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Added detection code that tries to determine if the annotation content streams coordinates are defined in annotation space or in page space. The annotation rectangle which is it's absolute page location is compared against any shape in the content stream. If the rectangle doesn't contain any content then we have to assume the content was written in annotation space.
Several long standing bugs related to this are now rendering correctly.
The system property org.icepdf.core.annotations.interactive.enabled is now respected by the widget annotations.
Show
Patrick Corless
added a comment - Added detection code that tries to determine if the annotation content streams coordinates are defined in annotation space or in page space. The annotation rectangle which is it's absolute page location is compared against any shape in the content stream. If the rectangle doesn't contain any content then we have to assume the content was written in annotation space.
Several long standing bugs related to this are now rendering correctly.
The system property org.icepdf.core.annotations.interactive.enabled is now respected by the widget annotations.
The checkboxes in question are drawn using a coordinates system that isn't correctly reflected by the appearnce streams matrix. As a result they are being drawn in the incorrect location. I think it might be possible to keep track of the bounds of the shapes being drawn and compare them against the Annotations bounding rectangle object. If they are not contained we can compensate.
PDF/A read only
There is actually nothing the PDF/A specification that states that states that it should be read only. Adobe has been criticized for adding the "read-only mode" to the viewer if the attached meta data is labeled PDF/a. The specification states how the file should be written, not how it should be viewed.
The form fields can be set as read/only using the appropriate annotation flag and the viewer will respect it.
It is also possible to use the system property org.icepdf.core.annotations.interactive.enabled=false to disable annotation interactions. There is however a bug in the current widget implementation which will be fixed beofre the 6.2 release.