Haz
@haz.dev
– Author of @ariakit.org
– Previously Automattic, WordPress
– JavaScript, CSS, Accessibility
– Autistic, dad, he/him
– Previously Automattic, WordPress
– JavaScript, CSS, Accessibility
– Autistic, dad, he/him
If you want to support us too: github.com/sponsors/ari...
Sponsor @ariakit on GitHub Sponsors
Toolkit for building accessible web apps with React
github.com
November 12, 2025 at 3:54 PM
If you want to support us too: github.com/sponsors/ari...
Honestly, I don't see any path for Gecko to improve. The only option I see is for Mozilla to use Google's investment to join forces with WebKit or Chromium and discontinue Gecko for good.
Firefox adopting Blink as its rendering engine would be a great step forward for the web.
Firefox adopting Blink as its rendering engine would be a great step forward for the web.
October 24, 2025 at 11:02 AM
Honestly, I don't see any path for Gecko to improve. The only option I see is for Mozilla to use Google's investment to join forces with WebKit or Chromium and discontinue Gecko for good.
Firefox adopting Blink as its rendering engine would be a great step forward for the web.
Firefox adopting Blink as its rendering engine would be a great step forward for the web.
It was the solution to IE's dominance. So yes, if Chromium becomes problematic, it should be replaced with something better, whether it's a fork or not.
October 24, 2025 at 7:46 AM
It was the solution to IE's dominance. So yes, if Chromium becomes problematic, it should be replaced with something better, whether it's a fork or not.
But then you learn that Google is Firefox's biggest investor. In the browser engine wars, you're left choosing between Google and Apple. To me, they're equivalent.
October 24, 2025 at 7:39 AM
But then you learn that Google is Firefox's biggest investor. In the browser engine wars, you're left choosing between Google and Apple. To me, they're equivalent.
I see that some people make this choice based on ideology. I can understand that. I choose some of the services I use based on that too (I'm not posting on Bsky because I think it's technically superior, for example).
October 24, 2025 at 7:39 AM
I see that some people make this choice based on ideology. I can understand that. I choose some of the services I use based on that too (I'm not posting on Bsky because I think it's technically superior, for example).
I don't have any attachment to browser engines. I think new browsers should choose what's best for them and their users. Right now, that's Chromium. If Firefox becomes better than Chromium at some point, I'll recommend it. That's not the case today.
October 24, 2025 at 7:39 AM
I don't have any attachment to browser engines. I think new browsers should choose what's best for them and their users. Right now, that's Chromium. If Firefox becomes better than Chromium at some point, I'll recommend it. That's not the case today.
Firefox's problem isn't the number of users. It's an investment issue. I reported a few issues on Bugzilla several months ago, and they're still open. I also reported issues on Chromium that were fixed within a week.
October 24, 2025 at 7:39 AM
Firefox's problem isn't the number of users. It's an investment issue. I reported a few issues on Bugzilla several months ago, and they're still open. I also reported issues on Chromium that were fixed within a week.
You shouldn't expect more people to use your open-source project to improve it. Make it better first, and I'd be more than happy to recommend it.
I don't care about Chrome. I care about performance and feature support, and Chromium is currently superior on both fronts.
I don't care about Chrome. I care about performance and feature support, and Chromium is currently superior on both fronts.
October 24, 2025 at 7:39 AM
You shouldn't expect more people to use your open-source project to improve it. Make it better first, and I'd be more than happy to recommend it.
I don't care about Chrome. I care about performance and feature support, and Chromium is currently superior on both fronts.
I don't care about Chrome. I care about performance and feature support, and Chromium is currently superior on both fronts.
And I haven't even mentioned the forced lock-in Apple imposes on iPhone, since you can't use anything other than WebKit. Even if Chromium isn't perfect, claiming anything else is better ignores that the alternatives are just worse.
October 23, 2025 at 10:11 PM
And I haven't even mentioned the forced lock-in Apple imposes on iPhone, since you can't use anything other than WebKit. Even if Chromium isn't perfect, claiming anything else is better ignores that the alternatives are just worse.
Gecko is years behind in modern features that will ultimately benefit accessibility. I'm working on some of them and Firefox is the only thing that's holding me back.
October 23, 2025 at 10:11 PM
Gecko is years behind in modern features that will ultimately benefit accessibility. I'm working on some of them and Firefox is the only thing that's holding me back.
Those are new features. We can choose not to use them and educate people accordingly.
What isn't easy to deal with (sometimes impossible) is an engine that doesn't support decade-old specs like combobox and aria-owns. WebKit added support for those only a few months ago.
What isn't easy to deal with (sometimes impossible) is an engine that doesn't support decade-old specs like combobox and aria-owns. WebKit added support for those only a few months ago.
October 23, 2025 at 10:11 PM
Those are new features. We can choose not to use them and educate people accordingly.
What isn't easy to deal with (sometimes impossible) is an engine that doesn't support decade-old specs like combobox and aria-owns. WebKit added support for those only a few months ago.
What isn't easy to deal with (sometimes impossible) is an engine that doesn't support decade-old specs like combobox and aria-owns. WebKit added support for those only a few months ago.
It hasn’t been an issue so far. If it does become one, another company can fork Chromium and take it in a different direction, just like Google did with WebKit.
October 23, 2025 at 9:00 AM
It hasn’t been an issue so far. If it does become one, another company can fork Chromium and take it in a different direction, just like Google did with WebKit.
Yeah, I interpret the specs and run extensive tests across multiple screen reader and browser combinations.
Even some of the W3C examples have issues, so you still have to test.
Even some of the W3C examples have issues, so you still have to test.
October 23, 2025 at 12:52 AM
Yeah, I interpret the specs and run extensive tests across multiple screen reader and browser combinations.
Even some of the W3C examples have issues, so you still have to test.
Even some of the W3C examples have issues, so you still have to test.
It doesn't matter how blazingly fast you can open blank tabs if page rendering is slow (as it is in WebKit). You spend most of your time rendering, not managing tabs.
October 21, 2025 at 4:39 PM
It doesn't matter how blazingly fast you can open blank tabs if page rendering is slow (as it is in WebKit). You spend most of your time rendering, not managing tabs.
As with tooltips, a hovercard should never be the only way to access information. For link previews, users on touch devices can open the page to view the content.
October 18, 2025 at 3:15 PM
As with tooltips, a hovercard should never be the only way to access information. For link previews, users on touch devices can open the page to view the content.
In that case, you're probably looking for the wrong component. If you need a hovercard to work on devices that don't support hover, use a popover instead.
October 18, 2025 at 3:15 PM
In that case, you're probably looking for the wrong component. If you need a hovercard to work on devices that don't support hover, use a popover instead.
