<IdleBot_4fae1f80>
horrible is returning SVG or PNG based on sniffing Gecko version in UA string
<samueldr>
isn't that comment in the CSS file "wrong", according to the logo page?
<samueldr>
what I mean is that it looks like there's already a workaround for that
<samueldr>
oh
<samueldr>
I understand it
<samueldr>
so even the "for browsers" version one uses features that firefox <83 doesn't support
<qyliss>
samueldr: correct
<qyliss>
there's no way (that I know of) to get that effect in SVG in Firefox <83
<samueldr>
I misread that initially and thought it meant that the inkscape mesh gradient was the conic gradient
<samueldr>
yeah, in my opinion as an ex-webdev, and still dabbling, SVG is "broken" on the web for multiple small reasons :(
<samueldr>
as soon as you stray from simple use cases it becomes a chore
<samueldr>
though it's saddening to see that a conical gradient is not a simple use case
<IdleBot_4fae1f80>
Web is broken for a miriad of small and not so small reasons… as soon as you stray from a static text websites…
<samueldr>
basically yes
<samueldr>
but what I mean here is that it's even broken where most developers would tell you "it's not" or "it totally works well"
<samueldr>
basic things, or things that should be basic just don't work as one would expect
<samueldr>
SVG backgrounds are (apparently, verified by a trusted third party) not rasterized, but always treated as a collection of elements in firefox!
<samueldr>
so the more complex your SVG background is, even if it doesn't resize, it will cause your rendering to be slower
<samueldr>
or something along the line, so basically SVG as background elements are a no-go when they are complex
<samueldr>
(sorry to completely go off-topic here :))
<samueldr>
so it's even broken when you assume the "basic brokenness" works
<IdleBot_4fae1f80>
Off-topic except as a reminder why browsers need to be isolated by a ten-meter concrete wall around each single-page-displaying instance…