[
https://issues.apache.org/jira/browse/PDFBOX-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237154#comment-14237154
]
Maruan Sahyoun commented on PDFBOX-2516:
----------------------------------------
I will change the logic for the retrieving the inheritable attributes.
Currently this is mostly that the attributes are either retrieved from the
field, it’s parent or the AcroForm.
{quote}
The field dictionaries may be organized hierarchically into one or more tree
structures. Many field attributes are inheritable, meaning that if they are not
explicitly specified for a given field, their values are taken from those of
its parent in the field hierarchy. Such inheritable attributes shall be
designated as such in the Tables 220 and 221. The designation (Required;
inheritable) means that an attribute shall be defined for every field, whether
explicitly in its own field dictionary or by inheritance from an ancestor in
the hierarchy.
{quote}
IMHO that shall be treated as to look up the hierarchy as the attribute might
be in one of the ancestors and not only it’s parent or the root.
> Further align AcroForms and Fields PDModel with PDF specification
> -----------------------------------------------------------------
>
> Key: PDFBOX-2516
> URL: https://issues.apache.org/jira/browse/PDFBOX-2516
> Project: PDFBox
> Issue Type: Bug
> Components: AcroForm
> Affects Versions: 2.0.0
> Reporter: Maruan Sahyoun
> Assignee: Maruan Sahyoun
>
> The PDModel for AcroForms and the fields being part of it
> (o.a.p.pdmodel.interactive.form) needs to be enhanced. Sample issues:
> - RadioButton and Checkbox don’t support DV entries although they should
> - inheritable attributes only support inheritance either form their parent
> or the root of the AcroForms model which is not inline with the specification
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
