So looks like 2 versions of floorp browser are available? Floorp Lightning and Floorp https://www.neowin.net/software/floorp-japans-privacy-centric-firefox-browser/
Yes I saw the Lightning release is available as a Flatpak in MX Linux' Discover software center. I've just installed it and set it up, including my customized userChrome.css file for an extensive test drive. Thanks for pointing this out
Well I didn't find anything special about the Lightning build, and it especially didn't "feel" any faster than the regular build, so I uninstalled it.
BTW, you might have missed this post, but I wondered why you believe Floorp is better than Waterfox. I now use Waterfox as my testing browser because I found Firefox way too bare bones. https://www.wilderssecurity.com/threads/floorp-browser-from-japan.451862/#post-3176413
https://flathub.org/apps/one.ablaze.floorp Was wondering if anyone translated the Privacy Policy? Privacy Policy is in Japanese which I'm unable to translate in FF ESR or LW browser because it is not a supported language yet.
Try this link maybe. https://flathub.org/privacy-policy Was taken directly from your link to the Floorp site. At the bottom via Privacy Policies.
In my case using Apparmor enforcement: This is just one example of many where floorp and firefox for that matter has either limited or no access rights - Read or Write - to user directories. That said, I'm keen to know more about this if it is a legitimate concern. Edit forgot to mention I don't use the Flatpak version.
And yet the same Pictures folder access attempt with MS Edge Flatpak browser (not apparmor-enforced): Not apparmor-enforced because I haven't found a way to do so with Flatpak browsers.
That is Privacy Policy for Flathub Translate this page for Floorp when downloading: https://docs.ablaze.one/floorp_privacy_policy/
Oy sorry about that. What I did was copypaste large sections of text into Google translate. Strangely, Google translate did not have the Japanese language option when you did DDG search, it wasn't listed. Only when I specified "Japanese-to-English" translation in search was when that came up. Here is the first portion of the text you linked. Spoiler: japanese to english floorp privacy policy first section Again, apologies for the wrong thing. Is this OK now?
@plat That's alright. I appreciate you taking the time to translate. My translation from Japanese to English on their Privacy Policy is very similar but not exactly the same. Not sure why but maybe I missed something when copy & paste sections of the page. Anyway thanks for your help.
OK cool. I decided to install Floorp with Sandboxie, and it seems to have more features than Waterfox. I don't know if they have implemented this themselves, or if these are hidden features in Firefox. But it sure looks like Floorp is the most feature packed Firefox fork.
Agreed, lots of features not seen in other Mozilla forks, and I don't know if they added these themselves.
Somewhat confused. In post #1 you mentioned you recently installed the available Flatpak in Linux openSUSE and in post #28 you installed Floorp Lightning version with Flatpak in MX Linux and then uninstalled it. Is Floorp available in any repositories yet or did you install Floorp from PPA or build from source code?
initially I used the Flatpak version in MX i guess, then uninstalled and went with the ppa version here Yes, see above.
I'm actually really liking Floorp so far. It has a lot more features that regular firefox ESR, and even more than Waterfox. I looks very polished.
You know, I'm starting to to think these are all hidden features in Firefox, I found out that you can add a lot of features via the about:config menu, it's so weird that Firefox hides them. But I haven't found a way to make Firefox put tabs on bottom of the screen. https://support.mozilla.org/en-US/kb/about-config-editor-firefox
very easy - there exist no switch to put this at bottom. if floorp can do its a script or css inside. for firefox you need userscript or css. be aware that such experience may change with the next update. mozilla do not care about user interceptions and how they modify their used browser. its on you to keep it current.
Based on my Apparmor profiles for both latest versions of Floorp and Firefox, there is nothing I can see extraordinarily different about Floorp, except that it looks to be more efficiently coded than Firefox.
Well Floorp add a lot of features Firefox doesn't have, requiring about the same, if not less, read/write access rights as Firefox, so they are doing something effectively well.
Try this: Code: /* IMPORTANT */ /* Get window_control_placeholder_support.css Window controls will be all wrong without it. Additionally on Linux, you may need to get: linux_gtk_window_control_patch.css */ /* Note: You must restart Firefox if you change the setting to select if firefox should hide toolbars in fullscreen. */ .titlebar-buttonbox-container{ position: fixed; display: block; top:0; right:0; height: 40px; z-index: 3; visibility: visible !important; } @media (-moz-gtk-csd-reversed-placement), (-moz-platform: macos){ .titlebar-buttonbox-container{ left:0; right: unset !important; } } @supports -moz-bool-pref("userchrome.force-window-controls-on-left.enabled"){ .titlebar-buttonbox-container{ left:0; right: unset !important; } } :root[uidensity="compact"] .titlebar-buttonbox-container{ height: 32px } .titlebar-buttonbox-container > .titlebar-buttonbox{ height: 100%; } /* Re-adjust window cotrols if menubar is permanently enabled */ :root[tabsintitlebar="true"]:not([inFullscreen]) #toolbar-menubar[autohide="false"]{ transform: translateX(0px); } :root[tabsintitlebar="true"]:not([inFullscreen]) #toolbar-menubar[autohide="false"] .titlebar-buttonbox-container{ height: 100%; } :root[tabsintitlebar="true"]:not([inFullscreen]) #toolbar-menubar[autohide="false"] .titlebar-button{ padding: 2px 17px !important; } @media (-moz-platform: windows){ #titlebar{ -moz-appearance: none !important; } } /* Move tabs below content */ #main-window > body::after{ content: ""; display: flex; } #main-window[inFullscreen]:not([inDOMFullscreen]) > body::after, #main-window:not([inFullscreen]) > body::after{ margin-bottom: calc(var(--tab-min-height) + 2 * var(--tab-block-margin,0px)); } #TabsToolbar{ position: fixed; display: block; bottom: 0; width: 100vw; height: calc(var(--tab-min-height) + 2 * var(--tab-block-margin,0px)); --tabs-navbar-shadow-size: 0px; } #TabsToolbar:hover{ z-index: 1 } #TabsToolbar{ background-color: var(--lwt-accent-color); } #TabsToolbar-customization-target{ width: 100vw; } .tab-background{ border-top-style: none !important; } /* Hide stuff that doesn't make sense with tabs below content */ #TabsToolbar > .titlebar-buttonbox-container, #TabsToolbar .titlebar-spacer{ display: none !important; } :root[inFullscreen] #toolbar-menubar > .titlebar-buttonbox-container{ display: flex !important; } @supports -moz-bool-pref("browser.fullscreen.autohide"){ #main-window[inFullscreen]:not([inDOMFullscreen]) > body::after{ margin-bottom: 1px; } :root[inFullscreen] #navigator-toolbox:not(:hover) .titlebar-buttonbox-container{ display: none !important; } }
maybe they have added/inserted some code of extensions, has to be simple, and to offer options for it instead of storage. its quite like the same as brave inserted an adblocker which they did not invented themself. not my job to judge, for me the base is important and currently based on v115 stands still for a year.