Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

869

Actually, Android 2.3 (2011) allowed downgrading through APKs.

But since Android 3 or 4, if you update, you're trapped unless you are ready to delete all app data.

Also, adb tends to be unstable and buggy (at least more stable than MTP. MTP is pure deprecated trash. )

Today, I updated Google Chrome from v74 to v78, just to find out that they have removed:

  • Ability to deactivate the annoying pull-down-to-refresh trap through chrome://flags
  • Ability to use list-view in tab switcher (shows URLs and more items per page, and is a stamina list instead of wobbly cards).

And people wonder why some people are reluctant to install the latest updates.

Actually, Android 2.3 (2011) allowed downgrading through APKs. But since Android 3 or 4, if you update, you're trapped unless you are ready to delete all app data. Also, adb tends to be unstable and buggy (at least more stable than MTP. MTP is pure deprecated trash. ) Today, I updated Google Chrome from v74 to v78, just to find out that they have removed: - Ability to deactivate the annoying pull-down-to-refresh trap through chrome://flags - Ability to use list-view in tab switcher (shows URLs and more items per page, and is a stamina list instead of wobbly cards). And people wonder why some people are reluctant to install the latest updates.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (11).
[–] • 1 pt

I just sent David Trainor (dtrainor@chromium.org), the genius who had this idea, an email (sorry for not quoting it. Markdown's blockquoting sucks.)

Hello, David.

I have a question about the commit 8cf3626120e3949f9718b626217bf93b8b6d2545 (chromium.googlesource.com).

“Remove enable-accessibility-tab-switcher from chrome://flags Leaving the swich in place as it is highly used as a command line value, but removing it to trim down chrome://flags size.”

My question is: What is the logical reason behind reducing useful options for the sake of trimming down chrome://flags size?

I am sorry to say that some people are very upset about this subtractive change. I hope it is understandable to you. If I knew it in advance, I would not have updated Google Chrome on my mobile phone.

I would not mind if chrome://flags had 20 times as many flags, because they are searchable anyway.

I would appreciate a logically comprehensive explanation of the removal. Thanks.

[–] • 0 pt

David Trainor has not replied yet.

Why are irrational fools like him allowed to mess with the browsing experience of millions of users?!

He can't even logically explain his change.