If it were me, I'd go for the <map> tag instead of fancy new CSS!
If it were me, I'd go for the <map> tag instead of fancy new CSS!
> image-based websites are massive
With the huge gains we've made in image optimization since <map>s were popular this isn't always true anymore.
This is a good approach, I think. It's kinda fine-tuned for reMarkable output, as it's mostly pure black or white pixels, but clearly they're fine with that. And the end result works quite well, and seems as easy or easier to implement.
This is all also kinda made moot by there being a link to an excellent transcript at the bottom. Accessibility needs are better covered by a straightforward alternate page than <map> alone.
I can't begin fathom how that could happen. It's not some fancy JS thing, it's a very simple CSS effect:
a:hover {
filter: opacity(0.5) !important;
}
.post a {
background-color: #35c;
mix-blend-mode: screen;
position: absolute;
display: block;
}
Do you maybe have a user-stylesheet that overrides something about links? But I can't think of anything that makes sense that wouldn't also break the non-hovering version too.Does opacity() combined with mix-blend-mode maybe not work right on your box? I'm not sure why it wouldn't, but you can convince me of just about anything by saying "Firefox does weird things on some GPUs".
But quite seriously, rejoice that you’re using Firefox. It has very few blending issues in general. I’ve found the Chromium family to be vastly buggier in this area, and I’ve learned when doing almost anything with filters and blending to develop with Chromium—previously I developed with Firefox and everything would just work, and then I’d test it in Chromium and discover some important bug or fundamental undocumented limitation in Chromium which meant I had to start again with a different approach, e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=992398 where a perfectly normal combination of things just stopped rendering the page after 8,192 pixels (which isn’t all that much); or for something more recent (earlier this year) look at the source of https://temp.chrismorgan.info/2022-10-03-hand-drawn-with-lin... and see some of the compromises I made for Chromium.
I was initially surprised to see it’s not transparent text overlaying the image, but apparently the text recognition is actually that good.