I love floorp. With the sideberry extension and the ability to completly hide the tabs, it looks awesome and utilize the screen to it’s maximum.
But were you able to use plasma integration extension with the flatpak version?
I had to install it from the ppa, but I’d rather use flatpak if the integration works.
I hardly use any default options in Floorp aside from maybe the split view. Most I do is in the userChrome and userContent. I use it because it simply runs smoother and faster than regular FF. It’s not a flatpak or a ppa either.
And I have no use for the plasma integration at all. For my workflow it makes more sense to have a bit of css to autohide the entire tool/bookmarkbar till hovered. If I want I could add a hide tabbar when only one, or include the tabbar in the autohide. Basically a browser with only a border ( bit thicker at the top for the mouse pointer trigger) but I’m fine with the way it is. O btw, the “gaps” within the main frame are due to the fact I’m using a custom user.js. The gaps are caused by anti canvas fingerprinting.
There are other ways to have pwa’s. You don’t especially need an in built functionality.
I tried PWAs for Firefox +4 months ago and couldn’t get it to work. Definitely share w/ the class if you have a recommendation for an equally simple PWA alternative for Firefox forks though.
We all have different preferences (YMMV) and unless a user tries out something, we’ll truly never know, right?
Might I suggest Zen Browser?
In the case of web browsers, I keep a balance — Zen Browser and Flashpeak-Slimjet — and yes, I have Falkon installed as well.
Zen browser has a couple of “issues” as discussed here.
Depends what you need the pwa for. And it depends how , I assume floorp, was installed. If it’s just separate windows you want next to an already running instance, you might have a look at the popup addon.
You could also make a full desktop app with the exec: floorp --class WebApp url
You could do the same but add a different profile to it. That has the advantages of completely different settings/addons…etc. Like so:
floorp --class WebApp url --profile /path/to/profile
You could try the mint webapp-manager if it’s available for your distro. But you’ll have edit the path to floorp a bit so that it can be recognized by the webapp manager
In either case, that pwa addon for firefox has been updated and it should work. No idea if it’ll work with floorp though.
Ahhh this is great.
I self-host various services that all point to my server’s IP, and since Floorp ignores the port #, I can only create a PWA for one self-hosted service.
With this suggestion, I can create Floorp profiles for each PWA which will give it its own context to launch
flatpak run one.ablaze.floorp --class WebApp http://192.168.1.223:3121/ --profile /path/found/via/about:profiles
