XFA Property Schema Defaults

Declared font, para, edge, color, comb, textEdit, hyphenation and margin nodes expose their supported schema attribute defaults in general JavaScript and FormCalc execution

Native HPDFXFAResolveFormInstanceProperty uses the same catalogue when the template omits an attribute, then applies the matching form-instance override

Effective values

const field = xfa.resolveNode("main.row[1].cell");
const face = field.font.typeface;
const width = field.border.edge.thickness;
field.font.size = "0.75pt";
field.font.weight = "";
field.border.edge.setAttribute("hidden", "presence");
const currentPresence = field.border.edge.presence;

Explicit template attributes and per-instance overrides take precedence over defaults, including an explicitly stored empty string; schema lookup does not insert default attributes into the source template

New repeated instances begin with schema and template defaults, whilst existing instances keep their own effective overrides

ClassSupported defaults
fontCourier, 10pt, normal weight and posture, 100 percent horizontal and vertical scale, zero baseline shift and letter spacing, no kerning, no underline, overline or line-through
paraLeft and top alignment, zero line height, indentation and spacing, zero widows and orphans, no declared tab stops
edgeSquare cap, visible presence, solid stroke and 0.5pt thickness
colorSRGB; white beneath fill and black beneath edge or corner
combZero numberOfCells
textEditAutomatic scroll policies, single-line in a field and multi-line in a draw; allowRichText follows associated exData content
hyphenationDisabled hyphenation and capital-word flags; push and remain counts of 3 and word count of 7
marginZero declared insets
checkButtonsize=10pt, shape=square, mark=default and allowNeutral=0
captionplacement=left, presence=visible and reserve=-1 for natural sizing

Catalogue values describe declared schema attributes; computed widget margin geometry can additionally depend on borders and font metrics

Corner defaults include inverted=0, join=square, radius=0in, presence=visible, stroke=solid and thickness=0.5pt; its default colour is black

Supported absent properties are initialized from these schema defaults during creation and repeated-prototype cloning

UI exposes common prototype attributes; passwordEdit defaults to hScrollPolicy=auto and passwordChar=*, whilst choiceList defaults to open=userControl, textEntry=0 and commitOn=select

Value exposes common prototype attributes, override=0 and an empty relevant attribute; supported scalar value classes expose common prototype attributes and an empty name

Image defaults to aspect=fit and transferEncoding=base64; line defaults to a backslash slope, arc defaults to circular=0 with angles 0 and 360, and line/arc/rectangle default to hand=even

Created image and graphic values retain native defaults, per-instance properties and actual draw consumers

Native scalar value creation initializes materialised value content from the field's current effective value

Created UI choices consume these attributes through actual runtime widget classification and saved field flags

Saved PDF output

The flatten style channel preserves fractional point values; AcroForm default appearance and border dictionaries retain sizes such as 0.75pt and 0.125pt rather than rounding them to whole points

Graphic edge widths retain fractional values in the PDF content stream, including the default 0.5pt width; numeric output remains independent of the system decimal separator

HPDFXFAFlatten accepts an absent draw callback for field-only extraction and skips graphic emission without calling an empty callback

Coverage

Created exData properties default to maxLength=-1 and transferEncoding=none, with empty contentType, href, id, name, rid, use and usehref attributes

The catalogue currently covers the classes listed above; additional schema classes, additional creation classes, inherited prototype defaults and computed widget margins remain separate integration targets

Declared property lookup and mutation retain existing transaction, repeated-instance identity and value-budget behaviour

Rich text draws use effective font defaults and instance overrides during measurement and emission

Reference and related APIs

Default values follow the XFA 3.3 specification, including its context-dependent textEdit and color definitions

Native XFA Property DOM, HPDFXFAResolveFormInstanceProperty and Interactive XFA Runtime