Skip to content

FullBleed.DotNet 0.2.11: correct font selection across the CSS cascade

Latest

Choose a tag to compare

@krflol krflol released this 01 Nov 20:26
9e2bb5e

FullBleed.DotNet 0.2.11 embeds Fullbleed 2.5.51. Concrete font-family declarations now replace losing custom-property values correctly. An invalid winning custom-property value inherits the parent font. The managed API and native bridge source are unchanged.

dotnet add package FullBleed.DotNet --version 0.2.11

All 18 source jobs and 19 release jobs passed. Twelve package consumers cover .NET 8–10 on Windows x64, Linux x64, Intel macOS and Apple Silicon. Their thirteen font witnesses have matching saved PDF and PNG bytes. The actual public 0.2.10 NuGet reproduces eleven incorrect font selections and two healthy controls; this release corrects the eleven and preserves both controls. Existing counter, page-font and document checks remain in place.

A fresh Windows .NET 8 consumer installed the signed public NuGet and passed the font, counter and page-font checks. Three README examples ran from that public package. Its 57 payload entries match CI; NuGet's verified repository signature is the only added entry. The evidence archive retains source, actual output, controls, visual review and verification summaries.

The attached NuGet is the unsigned CI artifact; NuGet.org provides the signed package. These results cover the stated fixtures and runtime matrix. C# component authoring remains alpha.

Change review. Source: 9e2bb5ed90b3f5925f56881b7eb8b1444f938ac8.

The source run needed one infrastructure-only retry: an Intel macOS runner could not resolve GitHub’s download host during setup, before checkout. That job and its dependent comparison then passed on the same source/package. The evidence archive retains the original failure log and both attempts. The publishing workflow ran once.