From 7d601a711f3f77f49c97e2579b725fc683f8cdb4 Mon Sep 17 00:00:00 2001 From: Rohan Kumar Date: Sun, 15 May 2022 17:39:22 -0700 Subject: [PATCH] Stop using the "contain" CSS property More trouble than it's worth. --- assets/css/main.css | 6 ------ 1 file changed, 6 deletions(-) diff --git a/assets/css/main.css b/assets/css/main.css index c62fbdb..2502a26 100644 --- a/assets/css/main.css +++ b/assets/css/main.css @@ -211,12 +211,6 @@ section[itemprop="mentions"] > figure { margin: 0; } -section[itemtype="https://schema.org/ImageObject"] figcaption, -figure[itemtype="https://schema.org/ImageObject"] figcaption, -div[itemprop="articleBody"] > figure:not([itemtype="https://schema.org/ImageObject"]) { - contain: content; -} - /* browsers make monospace small and unreadable for some dumb legacy * reason and this somehow fixes that without overriding the user's * font size preferences. */