Nick Chomey

@janvlug@mastodon.social @jrf_nl@phpc.social @Gina@fosstodon.org @janl@narrativ.es Agreed. PWAs are the way forward. But your comment about librewolf compatibility is misguided - this is a discussion about policy, not individual developer decisions about which apis to build upon. Also, Firefox has failed to implement some important pwa apis, so I have to figure librewolf suffers from that as well.

@loucyx ooh, this is nice. Thanks for bringing it to my attention!

@spartanatreyu @jimniels Here's an example, which seems to handle nav and aria without any separate js script. Just a few declarative attributes. https://codepen.io/nickchomey/pen/RNoWPZz I did it from my phone, so perhaps the aria isn't correct. But surely you can see how much simpler this is, and better ux not having a full nav. Just a one-time 10kb download of datastar, which affords endless other capabilities. Edit: I added an implementation with the Invoker Commands API. Probably best solution of all

@jimniels I came across this post on HN. it's a nice instinct to try to be js-free, but then you're just using js to manipulate your history, which is surely far more blasphemous than a sprinkling of js to show/hide a menu. Especially when you're doing a full nav for this. I beg you to check out Datastar. It's precisely what you're looking for. It's more powerful than htmx + alpine js, and smaller than both. You could just have a few declarative html attributes that show/hide the menu.

@janvlug@mastodon.social @jrf_nl@phpc.social @Gina@fosstodon.org @janl@narrativ.es You're missing the real story here: APPLE is the enemy of PWAs and an open, powerful web. Not Google. So much more here: https://open-web-advocacy.org/ https://infrequently.org/series/browser-choice-must-matter/