v1.28.1

gildas-lormeau/SingleFilev1.28.1Oct 4, 2026by gildas-lormeau

Upgrading?

AI Summary

Updated single-file-core to version 1.6.24 to support nested fonts, script-generated fonts, and improved CSS specificity. Updated privacy policy to include WebDAV, S3, and REST API destinations. Fixed multiple font parsing and DOM manipulation bugs.

Key Highlights

  • Updated single-file-core (1.6.24) with support for nested fonts, script-generated fonts, and improved CSS specificity
  • Updated privacy policy to explicitly mention WebDAV, S3, and REST form API destinations
  • Fixed fonts being incorrectly removed when using 'remove unused fonts' due to nested style rules
  • Fixed `url()` parsing in CSS at-rules like `@scope`, `@starting-style`, `@keyframes`, and `@page`

Full Release Notes

### Changes

- single-file-core is updated from 1.6.22 to 1.6.24, see https://github.com/gildas-lormeau/single-file-core/releases/tag/v1.6.23 and https://github.com/gildas-lormeau/single-file-core/releases/tag/v1.6.24 (fonts declared in nested rules, `font-width` and `tech()` sources, fonts created by scripts, specificity per spec, zip.js 2.23.0)
- The privacy policy mentions the WebDAV, S3 and REST form API destinations

### Fixes

- With "remove unused fonts", a font named only in a nested style rule was removed, and the text fell back to another font
- A `url()` in `@scope`, `@starting-style`, `@keyframes` or `@page` was not saved in the page
- A font created by a page script with `new FontFace(...)` could be saved with an invalid family name
- Removing a script, a `<noscript>`, a resource hint or a hidden input from the body shifted the position of the elements after it, so `:nth-child()` and similar selectors matched other elements
- In Firefox, a stylesheet imported by a `<style>` element was applied empty in a self-extracting archive, so pages loading Google Fonts this way lost their fonts

Related Repositories