Why is this so hard to understand? Why are they so against just making it work like it's supposed to? PWAs are actively useful and great and this is just frustrating.
I feel there will be more sites where the URL won't matter or where the user will prefer simplicity to control.
I use Google Maps 99.99% in PWA mode and never mourned the lack of the URl bar, especially as I can open the site in normal browser mode anytime I ever want the full controls.
1) There's no clear definition of what it's "supposed" to. Not everyone who uses the term PWA wants the same things.
2. Some things are just a lot harder to implement than others.
2. It is not harder to implement a button to show the toolbar menu
In all case, it should be (it already is by the spec!) a developer option, not something enforced by the browser.
Who are you to tell the user how their device is supposed to work?
Is it? I thought they made money by taking it from theGoogs to be the "default" search when theGoogs probably thinks of it as ensuring there is "competition" so they are not tagged as monopoly. Same as the payment they make to Apple
I am thoroughly finished with them as an organization; hopefully they represent the end of an ugly era, which to my recollection began in about 2013. I will not mourn their inevitable slide into complete irrelevance and financial insolvency.
It's unironically better than Chrome in nearly every way, except dev tools.
And they wrote their comment using Chrome or some skin. Which they have used for a decade. Because the button on the left seemed off on Firefox compared to Chrome (always something). So fuck Firefox.
On hacker news.
Crazy.
You have the wrong expectations toward HN :) It's a lot less frustrating if you correct them.
It's the community forum for a US-based, web-heavy startup accelerator, not a "hacker's corner" in terms of the original scene. The priorities and values and interests do differ.
In chrome, there is always a button to "bring back" the app from pwa into a browser tab (really nice). There is the option to open links directly in the pwa, you can access your extension from a small icon. I read that on the specs there might be an option to keep tabs around, for things like notion where your might need tabs (that would be really cool).
Overall, I'm impressed positively. Apple it's right to be scared about those, I would use PWAs for everything that's online for sure, for stuff that's offline probably too.
Excalidraw is great as PWA :)
Isn't Electron based on Chromium?
It's a weird side because I have no control over an app using electron or not.
https://connect.mozilla.org/t5/ideas/bring-back-pwa-progress...
So far Firefox has been a bit rocky, I don't seem to be able to open Jira tickets. Some might consider that a feature, but my job isn't one of them. That's shaken my faith in Firefox more than a bit.
But I had no (extra) trouble opening Jira tickets a few months ago when working with a partner integration.
So, Jira definitely should work on Firefox.
Hopefully they keep building from here & do full PWA and then from there to an answer to Electron!
Sorry, but I don't trust Google's push to Manifest V3.
