From 8ba79ba7690c1f1455433681c0edec8829abe446 Mon Sep 17 00:00:00 2001 From: Rohan Kumar Date: Sat, 4 May 2024 17:41:11 -0400 Subject: [PATCH] Update Weasyprint compatibility Reflects recent changes to styling of
. --- content/meta/site-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/meta/site-design.md b/content/meta/site-design.md index 4568277..b36abf5 100644 --- a/content/meta/site-design.md +++ b/content/meta/site-design.md @@ -117,7 +117,7 @@ I support compatibility to the following degrees: - Fully operable in textual browsers, litehtml, and NetSurf. Some issues (e.g. missing `
`) 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: