thats why i wrote "i am pretty sure", not: "i know". Since Quantum i could reduce extensions from 45 to 28 because Firefox got a lot of features added in the past 4 years the list did not changed since 2020, versions numbers did (dont mind on the numbers, the firefox built-in extensions (8 ) and disabled (3) are counted too) most people have several blockers installed because they are not able to manage one of them. thats my overall experience across the forums. some of them are outdated and discontinued, although they are in the store and untouched for years. some may still work but user wont catch the errors behind. thats why i like the chromium extension manager because it presents extension errors, but not firefox. for me to name "Redirect Bypasser" which causes errors in chromium, but not visible and not in the functionality i use. it may fail on different features i dont use so i dont see. same extension is present in firefox and i noticed some minor nifties and i am not able to fix it. so extensions from 2019/1018 or earlier have issues, thats an undenyable fact. i dont have doubt that most of extensions have only one special function. major problem of such extensions is beeing over time. they are not used that much so the author in most times forget to update its code. those will fail in time, sooner than later. maybe the list of used extensions of plat will enlighten us.
Huh? Brummelchen, I only use 3 ext. for Firefox. uBO, Skip Redirect and ClearUrls. I was remarking on the large number of ext. reported earlier--I never had that experience personally. No big deal.
Here you are: Tabs on Bottom (with custom css from here): https://dl.dropboxusercontent.com/s/uqcgoi88ihrabc4/Screenshot_tabs-on-bottom.png To close a tab: middle-click.
No problem, I read "i am pretty sure you have a lot of duplicate functions" a bit differently. I haven't cleaned up in a while, extension wise. I see we use a few of the same ones. Code: List of Extensions (Fri Aug 13 2021): 1. About Sync 0.0.52 2. Add-on List-o-matic 9000 1.5 3. Amazon.com 1.3 4. Auto-Sort Bookmarks 3.4.1 5. Bing 1.3 6. Bookmark Dupes 6.4 7. Bookmark Manager and Viewer 0.2.6.1 8. Bookmarks Organizer 3.1.0 9. Cookie Quick Manager 0.5rc2 10. Copy Link Text 1.6.1 11. Copy PlainText 1.12 12. Copy URL To Clipboard 6.2.0 13. Dissenter Extension 0.1.5 14. Don't **** With Paste 2.7 15. DuckDuckGo 1.1 16. eBay 1.3 17. Edit 1.8 18. Enhancer for YouTube™ 2.0.104.13 19. Erinome RSS Detector 1.0.2 20. Exif Viewer 3.7.5 21. F.B Purity - Cleans up Facebook 33.2.0.0 22. FoxyProxy Standard 7.5.1 23. FoxyTab 2.15 24. Google 1.1 25. History in Threads 2.3.4 26. Image Search Options 3.0.12 27. IP Address and Domain Information 4.0.6.0 28. JSON Lite 21.3.0 29. JSONView 2.3.0 30. Link Alert 2.0.1 31. Location Bar Characters 1.0.0 32. Nimbus Screen Capture: Screenshots, Annotate 15.6.9 33. Picture Exif Cleaner 1.0.4 34. Plasma Integration 1.8.0.1 35. Print Edit WE 28.4 36. Resurrect Pages 8 37. Selection Context Search 5.19 38. Selection Context Search - mini #1 1.5 39. Selection Context Search - mini #2 1.5 (Disabled) 40. Selection Context Search - mini #3 1.5 (Disabled) 41. Show External IP 1.0.6 42. Show/Hide passwords 0.4 43. Text Link 6.1.2 (Disabled) 44. uBlock Origin 1.37.2 45. Update Scanner 4.4.0 (Disabled) 46. User-Agent Switcher and Manager 0.4.7.1 47. Wikipedia (en) 1.1 Some of these are search engine stuff. There are a few I was testing or thinking of removing. I used to have a boat load of extensions.
@Buddel @Brummelchen good news, fellas. i've found the alternative. heck, i already had it, i just didn't know i did. "ublock filters - annoyances" does the trick. we don't need an extension for it. so i guess that's why the "google search link fix" extension is discontinued.
URL tracking (not only for Google) can be countered with the "$removeparam=" modifier in uBO. Relevant lists: AdGuard URL Tracking Protection (in uBO's default Privacy section). Actually Legitimate URL Shortener Tool.
I'm using 7 extensions in real-time and 2 extensions on demand in Vivaldi. What I don't like about Chromium based browers is that you can't disable auto-updating of extensions, in Firefox you can set it to only update extensions manually. So at least they got that part right. But anyway, I don't care what anyone says, the more extensions you are using, the more you at risk. I do believe that Chrome/Chromium will soon offer Site Isolation for extensions, which means that it should give more protection against malicious extensions, but I'm not sure how it works. I'm not sure if Firefox offers the same. https://9to5google.com/2021/07/20/chrome-site-isolation-extensions-android/
thanks, nico. yeah, i know that but the reason i used to use gslf was to prevent search engines from modifying search result links when they're clicked. with ubo annoyances filter list enabled, the links remain intact after they're clicked, so you can directly copy them via right click on the search results page.
Is that this filter: Code: www.google.*##+js(set, rwt, noopFunc) https://github.com/uBlockOrigin/uAssets/issues/7960
Sorry forgot to reply, but it's very unclear, do you need to download some extension? Also, looking at your screenshot, it's not truly tabs on bottom, I mean that the tab-bar should be located in the bottom of the window, just above the Windows Taskbar. Anyway, this should be a standard feature like in Vivaldi and Waterfox.
and it was removed. nevertheless it still works. i will see how far. i am not sure if i switched for testing purpose in desktop beta or nightly. but i added it to my android nightly because i cannot add my own extensions, only official. my bad, just read about "91" and missed the "v" sorry. i need to explain, no you. 47, sub 8 for the search engines and sub 4 for disabled. you have 36,. thats a nice number. what i can tell you: - Bookmarks Organizer - futile because of Bookmark Dupes - dupes is much much faster, its like car vs speed of light, i have 40.000 BM to work on. and it has lot more features. to find 404 or moved you are better advised to work with 404 Bookmarks. The extension from Sören is much too slow also in this part. - Bookmark Manager and Viewer - a try to replace "Show Parent Folder", but muuuuch slower. not sure if it has issues, working on 40.000 bookmarks it made my firefox crash because of the buggy favicon routines. so removed. i also removed the other one because of same issues. - Cookie Quick Manager - try "CookieBro" - User-Agent Switcher and Manager - neither nor recommended, makes pages behave wrong or buggy. what i have done for myself - a modified "clippings" which open as tab, not windows. i dont know why this jerk is adding settings but not the ability to switch those. "Awesome Cookie Manager" is a (reduced in functionality) compilation of my own from chrome store, but i think its getting buggy with the last builds. a really nice peace of work to work fast on cookies. oh, an update i did not realised on chromium (auto updates) well, i changed from "cookie autodelete" to "cookiebro" because its much easier to work on cookies and settings, CAD is also not really usable with its UI on android (smartphone), to big. and more granular.
Good find. "ublock filters - annoyances" has always been enabled here; now I know this filter list does the trick. Thanks a bunch, @imdb.
In the past it could be done with the now legacy Classic Theme Restorer, but since Mozilla now only uses Web Extensions, that's not possible any more. That's why the developer of that extension now maintains the repository CustomCSSforFx, which provides files and folders that you have to put in the 'chrome' folder inside your Firefox profile. A detailed set of instructions is provided here. Just download the latest zip-file from Releases and put the whole content in the 'chrome' folder (create it if not existing already). In 'about:config' you'll have to set 'toolkit.legacyUserProfileCustomizations.stylesheets' to 'true'. Tabs below main content can be achieved by un-commenting the line (in 'userChrome.css'): Code: /* @import "./css/tabs/tabs_below_main_content.css"; /**/ So that it becomes: Code: @import "./css/tabs/tabs_below_main_content.css"; /**/ Result (screenshot; dark theme): https://dl.dropboxusercontent.com/s/qt2xuxbe78hgqns/Screenshot_tabs-below-main-content.png Tabs below the navigation toolbar: Un-comment the line: Code: /* @import "./css/tabs/tabs_below_navigation_toolbar.css"; /**/ So that it becomes: Code: @import "./css/tabs/tabs_below_navigation_toolbar.css"; /**/ I'll have to admit there's quite a learning curve, but once you've set it up, you'll be able to achieve a lot of UI tweaks. It may break with new Firefox updates, but the maintainer is quick to fix it.
Aris deliver some basic styles and improve those with updates. how i would insert that collection: - extract all files into a subfolder (3 folder + 2 css files) - put all not needed stuff into comments: /* @import css */ - put own css into "my_userContent.css" or "my_userChrome.css" (next to userChrome/userContent) this is the default behavior if that collection. for updates only delete the 3 folders and replace them with the newer from collection, but NOT userChrome/userContent. all content goes to <profilefolder>\chrome\ you dont have to modify Aris codes if there is some unwanted code, put the corrections into my_userContent.css/my_userChrome.css. this will make css life much easier, no search/replace.
I'm guessing this was address to me. I count 47 Add-ons installed as listed; 6 are search engine, the 4 disabled are indeed installed. Two of those disabled extensions (Selection Context Search - mini #2 & #3 are for future use. The other two are in the process of testing. I just installed two more extensions today, Facebook Container & Firefox Multi-Account Containers to evaluate. Edit and Cookie Bro to evaluate.
I know, but lately (version3 ---> version 4) there have been some drastic changes (names/paths changed), so references in 'my_userContent.css' and 'my_userChrome.css' may have stopped working... Also, sometimes new css files are added and you would miss them, because they are not referenced in your own 'userChrome.css' and 'userContent.css'. That's why I always comb through the new versions of userContent.css/userChrome.css and make my changes (not many).
i had no closer look at v4 right now. currently the small amount of tweaks her are working up to firefox 93. v4 is complete lined up with proton and the removed tags. 3.3.2.1 <> 4.0.1 a closer look would tell me, that he removed all styles which are no longer applicable to firefox. ofc makes sense. he also fixed some bugs. i wont call it this way, he just removed outdated and not working code, in some cases i would say he changed code for reason, but still working. an hour later - i fixed his changes for the addons list. but this is due my usage of his css, my bad, cant blame him because he changed it. or i'll stick with the older build and deal with issues. myself also cleaned up the files. but it works like i wrote - his css and my afterwards changes (i use "ctr_corrections_content.css" as last file) those changes are really minor at all, compared to those who style their whole firefox like mad and need to rework a lot of 1000 lines. well done - thumbup
Thanks, but you gotta be kidding me, this is exactly my point. All of this work to get the tabs on bottom, ridiculous. No thanks, I will continue to use Waterfox as my test browser.
I was already expecting an answer like this. I don't mind fiddling with css. I'm somewhat autistic and I have all the time, haha. Btw, I sometimes use Waterfox (g3) as well and have the same css there.
Just use css. Go here, get the code, put the code in userchome.css Code: /* Source file https://github.com/MrOtherGuy/firefox-csshacks/tree/master/chrome/tabs_below_content.css made available under Mozilla Public License v. 2.0 See the above repository for updates as well as full license text. */ /* 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 */ /* Dummy variable to support both versions 89-90 */ :root{ --tab-block-margin: var(--proton-tab-block-margin) } .titlebar-buttonbox-container{ position: fixed; display: block; top:0; right:0; height: 40px; z-index: 3; visibility: visible !important; } :root[inFullscreen] #navigator-toolbox:not(:hover) .titlebar-buttonbox-container{ display: none !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-os-version: windows-win10){ #titlebar{ -moz-appearance: none !important; } /* Counteract -moz-appearance when maximized */ :root[tabsintitlebar][sizemode="maximized"] #navigator-toolbox{ padding-top: 8px !important; } :root[sizemode="maximized"] #toolbar-menubar:not([autohide="false"]) .titlebar-buttonbox-container{ top: 8px } } /* Move tabs below content */ :root:not([inDOMFullscreen]) #browser-bottombox{ margin-bottom: calc(var(--tab-min-height) + 2 * var(--tab-block-margin,0px)) } :root[inFullscreen]:not([inDOMFullscreen]) #browser-bottombox{ margin-bottom: 1px; } #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, #window-controls, /* Fullscreen window controls */ #TabsToolbar .titlebar-spacer{ display: none !important; } See the above repository for updates as well as full license text. */ /* Creates placeholders for window controls */ /* This is a supporting file used by other stylesheets */ /* This stylesheet is pretty much unnecessary if window titlebar is enabled */ /* This file should preferably be imported before other stylesheets */ /* Defaults for window controls on RIGHT side of the window */ /* Modify these values to match your preferences */ :root[tabsintitlebar]{ --uc-window-control-width: 138px; /* Space reserved for window controls */ --uc-window-drag-space-width: 24px; /* Extra space reserved on both sides of the nav-bar to be able to drag the window */ } :root[sizemode="fullscreen"] .titlebar-buttonbox-container{ display: none !important } :root[sizemode="fullscreen"] #window-controls{ position: fixed; display: flex; top: 0; right:0; height: 40px; } :root[uidensity="compact"][sizemode="fullscreen"] #window-controls{ height: 32px } #nav-bar{ border-inline: var(--uc-window-drag-space-width,0px) solid var(--toolbar-bgcolor); border-inline-style: solid !important; border-right-width: calc(var(--uc-window-control-width,0px) + var(--uc-window-drag-space-width,0px)); } /* Use this pref to check Mac OS where window controls are on left */ /* This pref defaults to true on Mac and doesn't actually do anything on other platforms. So if your system has window controls on LEFT side you can set the pref to true */ @supports -moz-bool-pref("layout.css.osx-font-smoothing.enabled"){ :root{ --uc-window-control-width: 72px; } :root[tabsintitlebar="true"]:not([inFullscreen]) #nav-bar{ border-inline-width: calc(var(--uc-window-control-width,0px) + var(--uc-window-drag-space-width,0px)) var(--uc-window-drag-space-width,0px) } } /* Source file https://github.com/MrOtherGuy/firefox-csshacks/tree/master/chrome/window_control_placeholder_support.css made available under Mozilla Public License v. 2.0 I use librewolf, but this works perfectly on FF.
