Bobby responded that the desktop PWA prototype that Mozilla built a few years ago got “some pretty negative feedback” in user testing and they didn’t have the bandwidth to take another crack at it.
I love how much people forget about this. PWAs were not liked when they came out. And that's putting it very very mildly.
And morover, at the time, people in general did not like PWAs as a concept. Independent of the browser. It's a bit funny when nowadays people always ask for PWA support, considering it was once yelled at until it was axed, and the whole concept ridiculed.
But it doesn't change the fact that some big players insist on PWAs instead of standalone Electron/whatever wrappers if you want anything close to a native desktop experience instead of a browser tab.
By some ppl. There were also ppl who did like them. As soon as the desktop support was axed, fans of the feature started complaining immediately.
at the time, people in general did not like PWAs as a concept. Independent of the browser
Again, I think this is a sampling issue, because my experience was the complete opposite.
And one of the key parts of PWA features was the "Progressive" part. The site works without those features and you don't have to use them so removing the support never made much sense to me.
I feel like they would've got more challenging questions had they asked here. They could've even done it on mastodon, with the hashtag #AskMozilla. Instead they chose to prop up the closed web 🥺
That may be a consideration, but what's important in the words of one mozilla employee in that thread is:
the future of the web. We work to push the industry forward and to push for decisions that enable people to shape their own online experience and that help consumers feel empowered and safe online.
I'd probably announce to people in other places that I'm going to host an AMA in a place that aligns more with my goals and that they're free to join and participate there.
Doing an AMA on mastodon would be a horrible experience for everyone. Others have pointed out the obvious difference in reach, blocks/defederation means some ppl may not even be able to participate, participants might never receive questions, users from different instances wouldn't be able to see sibling comments, etc.
Ah, I missed the bit about it being v120. I hope it shows the tabs from the same container first! I frequently have the same page open in multiple containers for testing.
Update to the bug I filed that was introduced in Firefox 116 - apparently, it isn't a bug:
I don't think this is a bug, its a side effect of the behavior for the ctrl|cmd + shift + T shortcut changing in 116 to reopen the last closed tab or window, in the order closed.
Technically, you closed a window when you dragged the tab out to a window, and then back to the original window. The exact same behavior happens if you use repeat those steps and use the ctrl|cmd + shift + N shortcut to reopen the last closed window.
There's an open needinfo for the author of the regressor, so I don't have much of a comment, but... it is very clearly a bug and very clearly a regression - Chrome doesn't do this (and actually has the newly claimed Firefox behavior) -- and neither did Firefox before it regressed.
quippd.com
Hot