HTML to PDF Compatibility

View Source

NativeElixirPdfUtilities.HtmlToPdf is a native document renderer for predictable server-side PDFs such as reports, invoices, labels, statements, and simple generated documents. It is not a browser engine and does not claim full browser compatibility.

For runnable templates, styling patterns, and caller-side error handling examples, see HTML to PDF Examples.

Unsupported or malformed input is rejected instead of being silently approximated. Rendering failures return a broad reason with diagnostic detail, for example:

{:error,
 {:invalid_css,
  %{
    stage: :css,
    reason: :invalid_css,
    message: ~s(line 18: selector "li >" is invalid or unsupported),
    line: 18,
    column: 1,
    source: "li >"
  }}}

The detail map always includes :stage, :reason, and :message. It includes :line, :column, and :source when the renderer can locate the source snippet. CSS is strict: unknown declarations and unsupported values fail with :invalid_css rather than being ignored.

HtmlToPdf Options

OptionSupported valuesNotes
:page_size:a4, :letter, or {width, height}Custom page sizes must be positive numbers. Tuples up to 20 x 20 are treated as inches for ChromicPDF-compatible label sizes; larger tuples are treated as PDF points.
:marginNumber of points or CSS length stringExamples: 24, "20mm", "0.5in".
:base_urlLocal path or file:// URLUsed for relative image paths. Remote HTTP fetching is not supported.
:stylesheetsCSS strings or local CSS file pathsConfigured stylesheets load before embedded <style> tags.
:default_fontFont family or fallback listDefaults to "Helvetica".
:fonts%{family: ..., path: ...} maps, keyword lists, or {family, path} tuplesTTF only. :weight and :style are optional. System font discovery is intentionally not required.

HTML Support Matrix

AreaSupported
Document wrappersdoctype html, html, head, body, style, meta, title
Blocksarticle, aside, div, footer, header, main, nav, section, p, h1 through h6
Inline textspan, strong, b, em, i, a, br; common named and numeric HTML entities are decoded
Listsul, ol, li
Tablestable, caption, thead, tbody, tfoot, tr, th, td
ImagesStrict img with required src
Attributesid, class, style, lang on html, metadata attributes on meta, href on links, src/alt on images, colspan/rowspan on cells
Linkshttps://, http://, and mailto: URI annotations

CSS Support Matrix

AreaSupported
SelectorsUniversal *, element, .class, #id, element.class, descendant, direct child, comma groups, :root, :first-child, :last-child, integer :nth-child(n)
CascadeSpecificity, source order, inline style priority, !important, inheritance for text styles, and CSS custom properties via var(--name)
Unitspt, px, rem, mm, cm, in, percentages for width/height/min-height, and unitless 0
Displayblock, inline, inline-block as a block formatting box, none, flex, inline-flex, grid, inline-grid
Box modelwidth, height, min-width, min-height, max-width, max-height, min(), aspect-ratio, box-sizing, margin, negative margins, padding, side-specific margin/padding, border, side-specific border-*, border-width, side-specific border-*-width, border-color, side-specific border-*-color, border-style, side-specific border-*-style, border-radius, border-collapse, background, background-color, accepted compatibility values for overflow: visible/hidden, no-op position: static/relative
Textcolor, font-family, font-size, font-weight, font-style, line-height, text-align, text-transform, vertical-align, line-break, word-break, word-wrap, overflow-wrap, white-space, letter-spacing; hex colors, common named colors, rgb(), rgba(), currentColor, and transparent backgrounds are accepted, with alpha ignored for painted text and borders
Page rules and breaksSimple @page blocks are accepted, page options control size; break-before, break-after, page-break-before, page-break-after with auto, page, or always; page-break-inside: auto/avoid is accepted
Flexbox subsetflex-direction, flex-wrap, gap, row-gap, column-gap, justify-content, align-items, align-self, justify-self, order, flex-grow, flex-shrink, flex-basis, flex
Grid subsetgrid-template-columns, grid-template-rows, grid-auto-columns, grid-auto-rows, repeat(), minmax(), grid-column, grid-column-start, grid-column-end, grid-row, grid-row-start, grid-row-end, grid-area, gap, row-gap, column-gap, justify-items, justify-self, align-items, justify-content, align-content

Layout Details

Block, list, table, flexbox, and grid layout are deterministic and intentionally narrower than browser layout. Tables use deterministic column sizing based on declared widths, available table width, and intrinsic unbreakable content, with support for collapsed borders, cell backgrounds, colspan, repeated headers, and missing trailing cells in shorter rows. Flexbox and grid support document-oriented text, images, and nested block-card items, not the full browser algorithms.

Pagination supports automatic page breaks, manual page breaks, page margins, basic keep-together behavior for emitted flow units, and repeated table headers when table bodies continue across pages.

Images support PNG, JPEG, and SVG data URIs, plus PNG/JPEG from absolute local paths and base_url-relative paths. SVG data URIs are rasterized to PNG with the lightweight resvg NIF using local in-process rendering; remote URLs and unsafe relative paths are rejected.

Fonts support built-in PDF fonts (Helvetica, Courier, Times-Roman and their bold/italic variants) plus explicit TTF embedding. Embedded fonts use TTF glyph widths, Type0/CID PDF resources, and basic Unicode mapping. Complex shaping for Arabic, Indic scripts, Thai, emoji sequences, and other advanced typography is not supported.

Unsupported Features

These features are intentionally outside the current renderer boundary:

  • JavaScript and runtime DOM behavior.
  • script, canvas, video, audio, iframe, and interactive form behavior.
  • Remote asset fetching.
  • CSS floats, absolute/fixed positioning, transforms, animations, media queries, pseudo-elements, and pseudo-classes beyond the documented selector subset.
  • Full browser-compatible table, flexbox, and grid algorithms.
  • Complex text shaping and bidirectional layout.

Validation Expectations

Automated tests cover parsing, CSS cascade, layout dimensions, pagination, PDF object output, images, fonts, links, and end-to-end rendering. Human visual validation is still required before accepting broad layout changes because PDF layout regressions can be visually obvious while remaining structurally valid.