Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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


Any person's first contact with a PWA is going to be in the full-chrome browser. The user has to voluntarily choose "install as web app" to actually lose the browser chrome. Not giving users this choice and opting them into a windowed mode forever makes PWA support largely useless -- just open the app from your bookmarks!


Isn’t there a middle where you don’t show the whole browser chrome by default and still allow access to the extensions? Maybe add a tiny button to show the browser UI or add a shortcut?


That is how it works in Chrome, right? Or am I going insane? When I open a web app I made with Chrome, there's a small icon in the top right of my window that opens the extensions dropdown.


From the Connect post I gather that a middle ground is basically the plan - you'll still have e.g. your extensions accessible, but there won't be a tab bar.


Which is an issue I haven't had with Chrome or Gnome Web ('s version of extensions), even with things like VSCode which overrides the title bar as well


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


I don't really understand this viewpoint, Chrome does show your extensions




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: