search

uazo / cromite

Cromite a Bromite fork with ad blocking and privacy enhancements; take back your browser!
https://www.cromite.org/
GNU General Public License v3.0
3.55k stars 85 forks source link

Keep Chrome Refresh 2023 avoidable #1035

Open highbaser opened 6 months ago

highbaser commented 6 months ago

This is a feature request about handling Chrome Refresh 2023 in the future.

Google started to introduce a UI refresh, starting from M115. The change is called "Chrome Refresh 2023". There are many bug reports, UX issues and negative feedback about this change and Google seems to be stubborn enough not to pay attention and force it upon all of its users. With M125 release, Google is expiring (and later removing) the flags that can disable the changes of Chrome Refresh 2023.

Chrome Refresh 2023 is already in latest Cromite (now: 124.0.6367.60) as it's based on M124 and the feature is turned on by default via "Cromite" flags. From a desktop user point of view it's an anti-feature that ruins the classic desktop experience (with mouse and keyboard), wastes vertical real estate, replaces icons to colorless unrecognizable ones. These changes are visually incompatible with a conventional desktop controlled by keyboard and mouse.

So my feature request would be to keep flags related to Chrome Refresh 2023 so Cromite users can turn them off. Also, a more sophisticated solution would be to provide a configuration option under Settings > Appearance to turn on/off the whole (or parts of this) UI change. It would also be a good idea to have these flags turned off by default, so an occasional user who first tries Cromite, could notice that Cromite has this ability and didn't blindly follow Google's path of anti-features. Also, this could indicate, that Cromite is a great alternative for Chrome users who are fed up with Google's arrogance to shove anti-features down on user's throats.

Chrome Refresh 2023 flags

Issues

Issues related to Chrome Refresh 2023, from the Chromium Bug Tracker.

Negative user feedback

Negative feedback from mostly advanced users who suffered a UX degradation because of Chrome Refresh 2023.

uazo commented 6 months ago

I wish there was so much commitment to privacy-related bugs!

So my feature request would be to keep flags related to Chrome Refresh 2023 so Cromite users can turn them off.

as long as it is maintained by google, it will be present in cromite. Try to understand me: I do not have the time or the inclination to deal with these things myself. If someone else takes the trouble to check and modify the code, welcome.

It would also be a good idea to have these flags turned off by default,

and then who is behind the various reports, "why is this button moved", "why is the text too small", etc.? no thanks, I prefer to invest my time in something more interesting.

highbaser commented 6 months ago

"why is this button moved", "why is the text too small", etc.?

This is called usability. It's no problem if something looks different on the UI from a particular version of a software, as long as there is a feature to customize it. This is called user freedom.

Flags are not maintained by Google. They're temporary and Chrome Refresh 2023 flags are now being expired, then they'll be removed. However, other projects like Supermium, Thorium, Brave are all planning to keep these flags in the long term. Check them out. You are free to merge their solution in the future.

markg85 commented 6 months ago

However, other projects like Supermium, Thorium, Brave are all planning to keep these flags in the long term. Check them out. You are free to merge their solution in the future.

Please do post your links to where those projects actually say that they will keep those flags.

It's a shitload of work to maintain out-of-tree patches, specially if it's something as invasive as the GUI itself. You can throw this on the usability claim and say "user freedom" but then you should back it up by offering your help to preserve that freedom.

highbaser commented 6 months ago

Please do post your links to where those projects actually say that they will keep those flags.

Brave: https://github.com/brave/brave-browser/issues/37770#issuecomment-2070963679 Supermium: https://github.com/win32ss/supermium/issues/506#issuecomment-2070225629 Thorium: https://github.com/Alex313031/thorium/issues/644#issuecomment-2073935659

It's a shitload of work to maintain out-of-tree patches, specially if it's something as invasive as the GUI itself.

Maintaining a browser fork is always a shitload of work. What's the point of it then? To make difference. Maintainers of Chromium forks make difference by keeping it somehow different from the original Chromium and Google Chrome. The value of the fork lies in these differences. If Google ruins the UX, a fork can keep the good old UX, so it will have more value than Chrome and be an alternative for users whom the changes disappoint. That's it. We're talking about the core motivatoin of maintaining forks.

uazo commented 6 months ago

However, other projects like Supermium, Thorium, Brave are all planning to keep these flags in the long term. Check them out. You are free to merge their solution in the future.

you can do it too. follow each commit and tell me which ones are related to that flag, I will gladly include them.

What's the point of it then? To make difference. The value of the fork lies in these differences.

is your goal, it is legitimate. mine is to learn and look for privacy issues, I think that is also legitimate.