Chromium and Nested Backdrop-Filters
If you’re like me, you sometimes get these small (often technical) problems, that you work on for so long — and you refuse to surrender.
I had this with CSS a couple of months ago:
I had a menu, that had transparency and blur, and then I also had a submenu that I wanted to have the same. But the submenu just. wouldn’t. blur!
It works perfectly in Gecko and WebKit — but after countless hours, I found the problem: If an element has a backdrop-filter, Chromium won’t let its children have it as well. 1
I had to design around it, and moved on with my life.
A few moments later…
I recently moved to Micro.blog. And one day I was scrolling down my timeline…
Then I opened the submenu:
There it was — the same bug! I’m not alone!
The fix
✉️ 🌱 To SigmaOS’ CEO: This Is What I Don’t Like About Arc’s Direction
I really, really like the Arc browser. But as I alluded to in this post, I have some reservations regarding it, and don’t feel like it’s going in a direction that I like. In the post, I said that I might try SigmaOS again — and I am. 1
I mentioned this in their community Slack, and their CEO, Mahyad, asked me what about Arc’s direction I don’t like. I must say, the dev team seems very active, nice, and open to input! So this post is my reply to his question.
(And here’s a link straight to the TL;DR at the bottom.)
Hi, Mahyad — and thanks for asking! I wrote a blog post called «I Just Want A Nice Browser!», which might give you a hint, heh.
And let me also say that I’m a bit worried about your direction as well — but I’ll come back to that. 😉
Two fundamentals I don’t love, but that I don’t need to go too much into
- I don’t love that Arc is built on Chromium — as I think Google has more than enough power over the web as it is.
- I’m not against supporting any VC funded company — but in combination with an unclear business model, I become more skeptical and worried if our incentives align. 2
My main issue, though, is regarding AI
The Prettiest Voice Since Allison Krauss
I Just Want a Nice Browser!
Two sad browser stories
I’ve followed the Spicy Takes™️ surrounding the Arc Browser recently, that started in the Ruminate podcast and went on to the MacStories Weekly Issue 408.
And I agree with most of what John Voorhees is saying, and also Matt Birchler, who said: «The Browser Company feels gross to me right now».
Much of it is about ethics and AI. In general I agree with them, but this subject won’t be the focus of this post. (I’ve written more about AI here and here.)
Instead I’ll tell my browser story, and explain why both Arc and Firefox makes me sad.
🌱 AI Is Just Different
The discussion around the ethics and legality surrounding AI has been a constant the last year — and it’s culminating in some important trials that’s coming up.
I won’t go into the entire thing here — I just want to focus on a specific argument that I often hear when it comes to the way these large models are trained. It oftes goes something like: «But how is this different from how humans have always been learning and iterating on previous knowledge?» or «The information was available on the open web, so it can be used for anything!».
I think these are terrible arguments.
Humans are allowed into shopping malls.
However, that’s simply not an argument for that cars should be allowed there as well — whether they’re driven by a human or autonomous.
A Couple of Chill, Mostly New, Indie Games
I love small, chill indie games.
- They’re cheap, and the money goes to small developers who needs the support.
- Many have short gameplay loops, that make them easy to fit into my schedule.
- And many of the ones I like have non-realtime gameplay,
- and that, coupled with low hardware demands, makes them well suited for playing on my laptop.
My MacBook isn’t a slouch - but it’s no gaming rig. So I love that I don’t have to worry about performance with these games - and those who don’t have native Mac ports, run perfectly fine through Parallells.