4 ms·

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

• echoangle 2y ago
  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?
  • Vinnl 2y ago
    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.
  • InsideOutSanta 2y ago
    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.
• its-summertime 2y ago
  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
• rchaud 2y ago
  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!
• bad_user 2y ago
  The complaint here is that Firefox won't do what Chromium does, and Chromium's extensions are active and reachable in installed PWAs.
• mary-ext 2y ago
  I don't really understand this viewpoint, Chrome does show your extensions