[FlorianRappl]

Types of Changes

Prerequisites

Please make sure you can check the following two boxes:

• I have read the CONTRIBUTING document
• My code follows the code style of this project

Contribution Type

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue, please reference the issue id)
• New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
• Breaking change (fix or feature that would cause existing functionality to change)
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

Description

0.8.0 in brief

0.8.0 is a rework of the layout core more than a feature drop. Inline content now forms real line boxes with one shared baseline. Floats are shared across block formatting contexts, so text wraps around them line by line. Shrink-to-fit sizing replaces the old heuristics, and flexbox follows the spec's algorithm for resolving flexible lengths. Styling now comes only from the computed style: every tag-name shortcut (bold <b>, hidden <script>, form-control looks) has been removed, and each missing default-stylesheet rule was fixed upstream in AngleSharp.Css 1.2.0. On top of that come a large batch of paint and text features: real tables (collapsed borders, fixed layout, captions), the full Unicode bidi algorithm, writing-mode, position: sticky, multi-column layout, intrinsic grid sizing, masks, border-image, backdrop-filter, blend modes, WOFF/WOFF2 web fonts, justification, hyphens and small caps.

What's cool about it

• The output is now honest. Because nothing is inferred from tag names and layout measures text with the same typefaces it paints with, what you see follows from the CSS. Earlier versions often looked right only by accident.
• It covers what real pages use. Modern CSS such as vertical text, sticky headers, grid with named lines, masks and blend modes now renders, not just CSS 2.1 boxes.
• It's pure .NET and deterministic. Bundled fonts and per-platform snapshot baselines make it fit server-side jobs like thumbnails, reports, email previews and visual tests, with no headless browser involved.

How close to "good and ready to use"

For static, controlled HTML (documents, reports, templates, cards, invoices, emails in Latin-script languages) it is usable now. A rough estimate is that it's around 90% of the way there for that use case.

For arbitrary pages from the web, it isn't there yet. The main gaps, from most to least important:

1. Text shaping (HarfBuzz). There are no ligatures, no kerning, no Arabic joining, no Indic scripts and no font-feature-settings. This is the biggest single blocker for typographic quality and international text.
2. Robustness in table and fragmentation edge cases. Anonymous table objects aren't built (stray cells and text are dropped), and column-span, break-* and paged media are missing.
3. Smaller layout gaps. These include grid track alignment (justify-content: center and similar), lines that should move down past floats, and writing modes inside flex or grid containers.

With 0.9 these items will be covered, too.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ FlorianRappl
❌ github-actions[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}