[X] My Assistant

Chrome cause habit ;(

Using multiple browsers for multiple needs and situations...

CHROME

DuckDuckGo has four recommended browser alternatives to privacy-poor Chrome. They are: Safari (free), Firefox (free), Brave (free), Vivaldi (free). Brave is even trying to create their own independent search database. That sounds pretty ambitious and you can see the beta for it at [brave.com] https://brave.com/search/

[spreadprivacy.com] https://spreadprivacy.com/how-to-remove-google/

DuckDuckGo has four recommended browser alternatives to privacy-poor Chrome. They are: Safari (free), Firefox (free), Brave (free), Vivaldi (free). Brave is even trying to create their own independent search database. That sounds pretty ambitious and you can see the beta for it at [brave.com] https://brave.com/search/

[spreadprivacy.com] https://spreadprivacy.com/how-to-remove-google/

Only "free" as in "free beer." You can't make your own build of Vivaldi or Safari. I don't trust or respect proprietary crap.
Also two of those are Chrome with lipstick and one is Chrome's older sibling.

This post has been edited by dragontamer8740: Aug 4 2021, 05:08

Only "free" as in "free beer."

It's going to get worse when web servers tempban any IP address trying to access without handshaking from an approved browser. I predict that is the direction sites will move towards.

its a real shame the only real alternatives to chrome besides firefox are differently labeled chromium, but its only understandable at this point no one wants to put up with making a fully featured browser with the state of the web I guess.
I do wish firefox would realize how important it is to not ruin their browser any further (god help me when they remove the proton ui toggles they still have in atm)

This post has been edited by cate_chan: Aug 6 2021, 15:23

its a real shame the only real alternatives to chrome besides firefox are differently labeled chromium, but its only understandable at this point no one wants to put up with making a fully featured browser with the state of the web I guess.
I do wish firefox would realize how important it is to not ruin their browser any further (god help me when they remove the proton ui toggles they still have in atm)

I have somewhat extensive CSS tweaks to proton, if you are interested in any of them.

They made tabs on bottom a real pain in the ass, though. Worse than it's ever been before. You need to do absolute positioning and never hide or always hide the bookmarks bar now.


This post has been edited by dragontamer8740: Aug 7 2021, 03:50

It's going to get worse when web servers tempban any IP address trying to access without handshaking from an approved browser. I predict that is the direction sites will move towards.

That's just "this site only works with IE6".

Nothing new.

I have somewhat extensive CSS tweaks to proton, if you are interested in any of them.

They made tabs on bottom a real pain in the ass, though. Worse than it's ever been before. You need to do absolute positioning and never hide or always hide the bookmarks bar now.

going to stay away from messing more with browser css for a bit longer till they actually get rid of the toggles and just pretend things are fine for now.
might take up that offer in the future though, do you host that css anywhere?

going to stay away from messing more with browser css for a bit longer till they actually get rid of the toggles and just pretend things are fine for now.
might take up that offer in the future though, do you host that css anywhere?

Nope, because Mozilla breaks shit constantly and I don't want to be beholden to others to fix things/update my browser in a timely manner.
I actually apply a couple small patches to Firefox sources and build it myself these days (to do things like making 'view image' open image in the current tab again). So updating is a bit of an ordeal for me - especially ever since they started using Rust, since that's another compiler to keep updated and it compiles really slowly.
It doesn't help that last time I built it, it wouldn't build in GCC 10 either so I had to start my build all over again using Clang.

Also my CSS is pretty cluttered/messy and does some things you may not like, like changing the UI font to a custom Tahoma edit I made that's just named differently so I can apply separate fontconfig rules to it. It also:

• moves the "new tab" button so that it is always on the leftmost side of the tab bar (so it doesn't move),
• forces all tabs to stay the same size always,
• moves the find bar up to the top (below the tab bar),
• makes icons more compact,
• Puts find bar buttons closer to the text entry box so less mouse movement is required,
• Hides those two or three little icons that usually squat on the righthand side of the URL bar,
• Probably other things that I'm forgetting, maybe disabling a few stupid animations.

You can probably just remove those things though.
In general, it makes things feel more like my Seamonkey configuration (and like Netscape Navigator).

[pastebin.com] https://pastebin.com/raw/MjWGaYHu
It also imports a secondary CSS file (made by someone else) to make the URL bar not horrible, which you can find here:
[github.com] https://github.com/WesleyBranton/Remove-Fir...ove_megabar.css

This post has been edited by dragontamer8740: Aug 7 2021, 20:42

Nope, because Mozilla breaks shit constantly and I don't want to be beholden to others to fix things/update my browser in a timely manner.
I actually apply a couple small patches to Firefox sources and build it myself these days (to do things like making 'view image' open image in the current tab again). So updating is a bit of an ordeal for me - especially ever since they started using Rust, since that's another compiler to keep updated and it compiles really slowly.
It doesn't help that last time I built it, it wouldn't build in GCC 10 either so I had to start my build all over again using Clang.

Also my CSS is pretty cluttered/messy and does some things you may not like, like changing the UI font to a custom Tahoma edit I made that's just named differently so I can apply separate fontconfig rules to it. It also:

• moves the "new tab" button so that it is always on the leftmost side of the tab bar (so it doesn't move),
• forces all tabs to stay the same size always,
• moves the find bar up to the top (below the tab bar),
• makes icons more compact,
• Puts find bar buttons closer to the text entry box so less mouse movement is required,
• Hides those two or three little icons that usually squat on the righthand side of the URL bar,
• Probably other things that I'm forgetting, maybe disabling a few stupid animations.

You can probably just remove those things though.
In general, it makes things feel more like my Seamonkey configuration (and like Netscape Navigator).

[pastebin.com] https://pastebin.com/raw/MjWGaYHu

cheers, saved for future reference when I will be forced into adding more css to get a usable browser without the toggles.
I used to compile firefox to mitigate some issues no one was fixing, was a massive pain in the dick to deal with, would rather avoid having to do that again.
for my particular issues I was patching for I switched to patching it with a gtk shim(issue is related to firefox calling some gtk function over and over again which causes a memory leak to explode). but thats not going to help with firefox ruining featurs like the view image stuff

It also imports a secondary CSS file (made by someone else) to make the URL bar not horrible, which you can find here:
[github.com] https://github.com/WesleyBranton/Remove-Fir...ove_megabar.css

atm I only have this for getting rid of it, which seems to work, forgot where exactly I got it from:

CODE

/* megabar mitigation */
#urlbar[breakout-extend] {
    top: calc((var(--urlbar-toolbar-height) - var(--urlbar-height)) / 2)!important;
    left:calc((var(--urlbar-toolbar-width) - var(--urlbar-width)) / 2)!important;
    width:100%!important;
}
#urlbar[breakout-extend] #urlbar-input-container { height: var(--urlbar-height)!important; padding:0px!important; }
.urlbarView { margin: 0px!important; width: 100%!important; }
.urlbarView-row { padding: 0px!important; }

This post has been edited by cate_chan: Aug 8 2021, 00:04

but thats not going to help with firefox ruining featurs like the view image stuff

You can actually fix that without recompiling, if you unpack omni.ja and edit a few files. But since they're generated from the sources, you have to fix it in more places than if you do it pre-compilation.
So since I'm already forced to compile it to use Alsa instead of Pulseaudio, it's not too much more of a burden than I already had to deal with.

atm I only have this for getting rid of it, which seems to work, forgot where exactly I got it from:

CODE

/* megabar mitigation */
#urlbar[breakout-extend] {
    top: calc((var(--urlbar-toolbar-height) - var(--urlbar-height)) / 2)!important;
    left:calc((var(--urlbar-toolbar-width) - var(--urlbar-width)) / 2)!important;
    width:100%!important;
}
#urlbar[breakout-extend] #urlbar-input-container { height: var(--urlbar-height)!important; padding:0px!important; }
.urlbarView { margin: 0px!important; width: 100%!important; }
.urlbarView-row { padding: 0px!important; }

Yeah, that works. I just didn't want to think about it.

Still annoying how clicking the URL bar selects everything, now… Seamonkey is so much more usable for me.

Still using chrome for its used widely.

cheers, saved for future reference when I will be forced into adding more css to get a usable browser without the toggles.

Oh yeah you'll probably want to remove one bit of my CSS because it makes installing addons a bit of an ordeal - the notification bubble telling you the addon was installed will strobe unless the stupid "hamburger menu" is un-hidden.
Comment out:

CODE

#PanelUI-menu-button {
  display: none !important;
}

You can actually fix that without recompiling, if you unpack omni.ja and edit a few files. But since they're generated from the sources, you have to fix it in more places than if you do it pre-compilation.
So since I'm already forced to compile it to use Alsa instead of Pulseaudio, it's not too much more of a burden than I already had to deal with.

at least for the time being I'm enjoying not having to deal with firefox finding a new way to break compilation(mostly the rust parts) each update, enough to pretend not to be bothered by things I cant get rid of fully without compiling it.

Still annoying how clicking the URL bar selects everything, now… Seamonkey is so much more usable for me.

wasnt that used to that behaviour to get bothered by it luckily, but they sure like to slip in needless functional changes like that all the time

I think part of the reason Chrome/Chromium has done well (besides Google's name and power behind it) is that they pretty much have never changed the UI in any appreciable way since launch over a decade ago.

Mozilla could learn a thing or two from them, but it's not any of the things they have been 'borrowing' from Chrome for the last decade. Don't pull the rug out from under the user. Or, if you must, do so extremely rarely. I know people who stopped using FF solely because it broke their workflows on every other release.

This post has been edited by dragontamer8740: Aug 10 2021, 16:25

speaking of the devil, seems firefox 91 (current latest stable still slowly making its way to all the distros) is the one that removed the porton style toggles.
should've never mentioned it

This post has been edited by cate_chan: Aug 12 2021, 00:37

speaking of the devil, seems firefox 91 (current latest stable still slowly making its way to all the distros) is the one that removed the porton style toggles.
should've never mentioned it

Yeah, I already knew that a month or two ago; that's why I doomsday prepped early and made my CSS in advance of the change.

I just assumed you knew and were going to wait until 91 hit.

So, apparently Firefox now survives restarting my X server but does so in such a way that you can't open any new windows until you kill all existing firefox PID's.