Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox Is Finally (Re)Adding Support for Web Apps

omgubuntu.co.uk

Post reply on HN
Print view View original

61–70 of 97 posts

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#61

Post by linsomniac »

Vinnl wrote: post #29
linsomniac wrote: post #11

Earlier quoted context omitted.

Yesterday afternoon I transitioned from Brave to Firefox. Brave was struggling, admittedly after a system uptime of 69 days, even after killing it brave would regularly struggle and do a whole ton of disc I/O, bringing my system to its knees. Rebooting fixes it, FYI, but it seems weird that "pkill -f brave" doesn't seem to resolve it. Slack also has similar struggles, this is under Ubuntu 22.04. So far Firefox has be…

If you have site-specific issues, if you're up to it it would be great if you could report it via the menu (or Help, on MacOS) -> Report broken site, or via https://webcompat.com .

Thanks, I'll give it a try! I also see in "Help" there is a "Troubleshoot".

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#63

Post by inetknght »

ctoth wrote: post #8

> Similarly, Rubino says web apps in Firefox will not use a minimal browser frame and will continue to show a main toolbar with address bar, extensions, bookmarks... 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.

> Why are they so against just making it work like it's supposed to?

Who are you to tell the user how their device is supposed to work?

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#64

Post by bad_user »

wtallis wrote: post #13
ctoth wrote: post #8

> Similarly, Rubino says web apps in Firefox will not use a minimal browser frame and will continue to show a main toolbar with address bar, extensions, bookmarks... 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.

PWAs that prevent you from getting at your browser extensions are an inherently user-hostile idea.

The complaint here is that Firefox won't do what Chromium does, and Chromium's extensions are active and reachable in installed PWAs.

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#65

Post by bad_user »

inetknght wrote: post #63
ctoth wrote: post #8

> Similarly, Rubino says web apps in Firefox will not use a minimal browser frame and will continue to show a main toolbar with address bar, extensions, bookmarks... 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.

> Why are they so against just making it work like it's supposed to? Who are you to tell the user how their device is supposed to work?

A frustrated user probably.

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#66

Post by bad_user »

Vinnl wrote: post #51
owebmaster wrote: post #35

Earlier quoted context omitted.

1. if 90% of the people don't want a toolbar in a PWA (I'm being generous about 10% wanting it), it makes sense to not have it 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.

I have learned a long time ago not to make claims about how hard it is to implement something in other people's projects - I get it wrong often enough about my own. (Also, I don't think there's a single "PWA spec".)

Firefox's UI can be easily tweaked with CSS. It's trivial, for example, to get rid of all chrome. The real problem is their ideological stance against PWAs.

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#67

Post by [deleted] »

ctoth wrote: post #8

> Similarly, Rubino says web apps in Firefox will not use a minimal browser frame and will continue to show a main toolbar with address bar, extensions, bookmarks... 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.

[deleted]

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#68

Post by nwienert »

JoshTriplett wrote: post #20
breckinloggins wrote: post #7

I’m not sure what Mozilla has been doing the last ten years but I’m fairly certain it has little to do with what users want. 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.

I will mourn the lack of a non-Chrome browser engine with enough market share to prevent Chrome from unilaterally changing the web.

Safari / WebKit.

It's unironically better than Chrome in nearly every way, except dev tools.

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#69

Post by makeitdouble »

nashashmi wrote: post #60
makeitdouble wrote: post #28

Earlier quoted context omitted.

There is clearly a use case for keeping the whole UI. But it is the major use case and should the whole product philosophy be based on it ? 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 co…

What if you want to copy and share the page?

I'd be fine with a 2~3 click operation to get the URL.

Which is basically how it works in Chrome in PWA mode: a few basic actions (get the URL, print, cast, adjust zoom etc) in a menu, and an option to punt it to the full chrome if needed.

Re: Firefox Is Finally (Re)Adding Support for Web Apps

#70

Post by mary-ext »

wtallis wrote: post #13
ctoth wrote: post #8

> Similarly, Rubino says web apps in Firefox will not use a minimal browser frame and will continue to show a main toolbar with address bar, extensions, bookmarks... 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.

PWAs that prevent you from getting at your browser extensions are an inherently user-hostile idea.

I don't really understand this viewpoint, Chrome does show your extensions
Post reply on HN