Post #2111698
2026-05-06 10:01 UTC
Replies (5)
-
@jaffathecake@mastodon.social 2026-05-06 10:08
@nachtfunke oh, Google had you all down as "strongly supportive" https://groups.google.com/a/chromium.org/g/blink-dev/c/iR6R7-nQeHI/m/gN4iEGEdAQAJ
-
@jsnkuhn@mastodon.social 2026-05-06 10:27
@nachtfunke @jaffathecake Not sure if this really matters at this point either but there is a web-platform-dx/developer-signals repo for this that few seem to be aware of. Maybe this is a better place to be collecting general developer sentiment: https://github.com/web-platform-dx/developer-signals/issues/556
-
@Lukew@toot.wales 2026-05-06 10:57
@nachtfunke @jaffathecake I think the big power developers do still hold is to just not use this API. The web isn't cast in stone (as much as people may think it is), if the usage stays low enough there's a chance it might unship in years to come, or at least go through changes to make others more onboard (idk if that's feasible here though).
-
@ragectl@hachyderm.io 2026-05-06 12:37
@nachtfunke @jaffathecake oh that's easy developers needed to keep using and supporting Firefox because open internet matters more than anything else. Sadly, majority of developers failed at that, just like they did with Internet Exploder.
-
@enthusiast101@ieji.de 2026-05-06 14:12
@nachtfunke @jaffathecake Honestly I think Chrome's dominance is severely overrated and that will continue to be the case unless Chrome decides to stop shipping Chromium as open source. Even if Chrome users are the majority, so long as Apple users still use Safari, and iphone (something which cannot use chrome) exists, Google cannot have utter dominance. Especially since I imagine many Chromium forks will not have this. Unless a website is going to only allow Chrome and other things that use this API, no website cannot make this mandatory. As much as I hate needing to account for browser differences when doing webdev, I am actually thankful for it in cases like this.