1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-23 12:52:10 +00:00

Update Weasyprint compatibility

Reflects recent changes to styling of <details>.
This commit is contained in:
Rohan Kumar 2024-05-04 17:41:11 -04:00
parent 549c6f4c87
commit 8ba79ba769
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479

View file

@ -117,7 +117,7 @@ I support compatibility to the following degrees:
- Fully operable in textual browsers, litehtml, and NetSurf. Some issues (e.g. missing `<details>`) might make the experience unpleasant, but all major functions work.
- Basic features in abandoned engines and Dillo. Some ancillary features may not work (e.g. forms for Webmentions and search), but users can browse and read.
[^0]: WeasyPrint doesn't support `details`, but I don't fully count this against my site's support for its engine because WeasyPrint targets non-interactive print media. Instead, I just ensure that the site makes sense in WeasyPrint without special `details` styling. Since my stylesheets define a border around `summary` elements, and since I they always start with the word "toggle", they make sense even when not rendered with special builtin styles.
[^0]: WeasyPrint doesn't support `details`, but I don't fully count this against my site's support for its engine because WeasyPrint targets non-interactive print media. Instead, I just ensure that the site makes sense in WeasyPrint without special `details` styling. Since my stylesheets define a border around `summary` and `details` elements, and since I they always start with the word "toggle", they mostly make sense even when not rendered with special builtin styles.
Some engines I have not yet tested, but hope to try in the future: