I’ve decided (after seeing the advice repeatedly!) to try and move away from Chrome and use FF instead. However I’ve immediately come across an issue which is a bit of a deal-breaker for me, and although I’ve looked into it, I haven’t seen an answer anywhere.

One of the best features in Chrome is the abilty to create a shortcut for an individual URL. This shortcut can then be placed on the desktop, start menu or quicklaunch toolbar (Win 10) and opened as if it were a program in its own right - so, no URL bar, no tabs, no bookmarks, just the site content.

I use this method every day for a number of different sites - Outlook, Gmail, Calendar, Keep, Sheets, Docs, etc, and it’s perfect. So much so that I usually forget that I’m technically opening all of these in Chrome at all, not least because the site favicon shows in the taskbar in place of the browser logo.

So, I assumed that FF would be able to do the same thing… but apparently not. Am I missing something? I’ve found people discussing old features like SSB (site-specific browsing) and PWA (progressive web apps), but as far as I can tell all work on this in FF has been discontinued.

I would maybe just put up with this, and use Chrome shortcuts for these sites, and FF for everything else, except that links clicked from within them will open in Chrome intead of FF, which makes for a confusing experience.

Anyone know of a good solution to this? Thanks in advance!

    • SanguinePar@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      3 months ago

      Oh wow, that’s great, I didn’t realise it was back on the agenda - thanks a lot! 👍

      That said, I found this line a bit surprising: “it’s not a goal to make it feel like you’re not in Firefox.”

      That’s a shame, because being able to have a website run as if I’m not in a browser is exactly what I want to achieve! Still though, at least they’re looking at the concept.

  • NutinButNet
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    It sounds like this is happening because your computer still has Chrome as the default browser. Assuming this is Windows: right-click one of the icons on the desktop, click Properties, then click Change and select Firefox.

    This will now set Firefox as the default browser for your computer and these icons should now automatically open in Firefox as well as any new ones you create.

    Creating an icon on the desktop is very similar in the process you would have done for Chrome too.

    The problem here is that you can’t create icons that are exclusive to Chrome or Firefox, as far as I know, since Windows chooses, by default, one app that will open these by default.

    Technically you could bypass this by right-clicking the desktop icon and then select “Open in” and then choose the other browser in case you need to open one in Chrome and the other in Firefox.

    • SanguinePar@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      3 months ago

      Thanks, but I’ve already changed default to FF - the icons are Chrome shortcuts though, so they will only open in Chrome. And I can’t see a way to make equivalent ones for FF, it just doesn’t seem to have the same functionality, in particular opening a link in a window with no tabs, bookmarks of address bar. Although I am going to check out an add on someone suggested that might do the job.

      Thanks though 👍

    • BearOfaTime@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      3 months ago

      Pretty sure if you set the path in the shortcut to the Firefox executable and passed the URL as a parameter it’ll open it.

      • SanguinePar@lemmy.worldOP
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        Yeah, but I don’t think it’ll open it in the way I want, with only the site content, and no browser furniture. I’ll try it, but I’m not sure. Cheers though 👍

  • Zedstrian@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    The loss of built-in PWA support was the biggest disappointment I had when switching from Chrome to Firefox, with the add-on solutions I tried having one problem or another in replicating my goal of making opening a handful of websites I had set to be PWAs look as much like regular applications as possible. While I wouldn’t switch back to Chrome in a second, and am still trying to get the rest of my family to make the switch, there’s a number of things Firefox needs to implement to remove the remaining roadblocks for people looking to make the switch away from Chrome or another Chromium browser.