Recent searches
Search options
#chromebug
New #CSS featues should make our lives easier, right?
Except for when they're buggy. Just hit (and filed) a Chrome bug 
https://issues.chromium.org/issues/405676714
Can you help me out, mastodon? 
Do you see the same result as below for this test, especially in Chrome/ Safari?
https://cdpn.io/pen/debug/KwKvRKr
Or finding red in rgb(0, 100%, 0%)?
Are you on a wide gamut display? You can check here https://wide-gamut.com/test
Retoots appreciated. Thank you! 
A "fun" Chromium bug I hit: https://issues.chromium.org/issues/373759987
`feComposite` intersection fails with `feTile` input... but only at certain levels of page zoom. 
This was supposed to be something I would use to make an inset shadow on an `img` https://mastodon.social/@anatudor/112435568084097010 depend on the `currentColor` set on that element.
+ something I would use for a `currentColor` rounded tabs outline https://mastodon.social/@anatudor/113301770171329917
Finally got around to filing a bug https://issues.chromium.org/u/1/issues/373410239
This breaks a lot of demos by adding what looks like ugly muddy grey background areas.
Also see interop issue https://github.com/web-platform-tests/interop/issues/756
CSS challenge: I’ve been working for a solution for leaders via SVG backgrounds with lines + stroke-dasharray: https://codepen.io/leaverou/pen/bGPMNRb?editors=1100
It *almost* works great except:
1. Is f*cked for long items
2. Needs a way to adjust the gap so that it always starts and ends with a dot (I have a hunch round() can help here)
No markup changes.
(Why not use circles + background-repeat: round no-repeat; ? Because there’s some kind of #ChromeBug that makes it print very badly)
What in Beelzebub's name's going on? My Slice! demo is in the
@codepen Spark and... it looks broken in the screenshot included with it!
Been told it looks broken in Chrome before https://x.com/rolandfranke/status/1803383982798540987 but I can't reproduce it in any Chromium version on Linux. Can you? What OS?
The live demo https://codepen.io/thebabydino/pen/GRaKbZo
Dave Millar How many more comments are needed to get the Chrome development team to take a bug seriously? 700 is not enough, apparently.
Looks like this is just a Chromium issue https://twitter.com/Benjamin_Aster/status/1789709940170305653
So I've filed a bug https://issues.chromium.org/u/1/issues/340018135
Hit a *very* strange #svgFilter #bug in #Chrome. There's this weird clipping for the result of `feComposite` using the `in` or `atop` operator (no issues for `over`, `out`, `xor`)... and it depends on the size of the viewport?!
https://codepen.io/thebabydino/pen/abxvwoo
All fine in Firefox.
All would be fine in Safari too, if it wasn't for another strange bug... https://mastodon.social/@anatudor/112048871998907011