Crosspost between alt.comp.software.firefox and comp.mobile.android.I think the change was in v147, I find it ok on a tablet, haven't really
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
I think the change was in v147, I find it ok on a tablet, haven't really taken much notice on phone
s|b wrote:
I think the change was in v147, I find it ok on a tablet, haven't really taken much notice on phone
Crosspost between alt.comp.software.firefox and comp.mobile.android.
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
Crosspost between alt.comp.software.firefox and comp.mobile.android.
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
<https://support.mozilla.org/en-US/kb/explore-firefox-android-menu>
Me neither. As far as I can tell, it wasn't a major paradigm shift.
But of course, other peoples' MMV.
Crosspost between alt.comp.software.firefox and comp.mobile.android.
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
<https://support.mozilla.org/en-US/kb/explore-firefox-android-menu>
Crosspost between alt.comp.software.firefox and comp.mobile.android.
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
<https://support.mozilla.org/en-US/kb/explore-firefox-android-menu>
Crosspost between alt.comp.software.firefox and comp.mobile.android.
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
<https://support.mozilla.org/en-US/kb/explore-firefox-android-menu>
s|b wrote:
Crosspost between alt.comp.software.firefox and comp.mobile.android.I think the change was in v147, I find it ok on a tablet, haven't really taken much notice on phone
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
On Sat, 28 Feb 2026 13:27:04 +0100, s|b wrote:
Crosspost between alt.comp.software.firefox and comp.mobile.android.
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
<https://support.mozilla.org/en-US/kb/explore-firefox-android-menu>
Got it back, for now, tnx to Reddit: <https://www.reddit.com/r/firefox/comments/1r36l47/ive_got_a_new_ui_on_firefox_for_android_which_im/>
| Settings | About | Firefox.
|
| Tap the logo multiple times until the developers settings are enabled.
|
| Go to Settings | Secret Settings
|
| There, toggle off : Toolbar Customization, Redesigned Toolbar, Composable Toolbar, and at the bottom, Tab Manager Enhancements ..
|
| Kill and restart Firefox.
|
| Edit: For some, settings take effect immediately without the need to kill and restart Firefox.
According to Mozilla, it can't be done. Liars.
<https://support.mozilla.org/en-US/kb/explore-firefox-android-menu#w_can-i-switch-back-to-the-old-menu-design>
s|b wrote:
Crosspost between alt.comp.software.firefox and comp.mobile.android.I think the change was in v147, I find it ok on a tablet, haven't really taken much notice on phone
What the hell did they do to the menu in Firefox for Android 148? They
went from a small, accessible menu to a gigantic monster.
Well - a *small* menu is *not* accessible on touch screens.
Interesting.
I looked at that reddit page and tried the changes but I don't see any difference.
Besides, I find it quite usable. Not gaudy or big.
And I do have 148 per the play store. Google Pixel 6a
I followed that procedure and so far it has not made any difference.
Just for giggles, I've powered my phone off and will start it up again
in a couple of minutes (I'm not that good at multitasking).
Interesting.
I looked at that reddit page and tried the changes but I don't see any difference.
Besides, I find it quite usable. Not gaudy or big.
And I do have 148 per the play store. Google Pixel 6a
but you're OK with this... monster?
When I'm in portrait mode on the tablet, and I "unfurl" the More and Extensions sections, it does take pretty much the whole screen
(9.1" 1440x2304).
On Sat, 28 Feb 2026 16:41:36 +0100, Arno Welzel wrote:
Well - a *small* menu is *not* accessible on touch screens.
It /is/ on my Pixel 10's touch screen.
On Sat, 28 Feb 2026 06:09:04 -0800, John C. wrote:
Me neither. As far as I can tell, it wasn't a major paradigm shift.
But of course, other peoples' MMV.
Et tu, John?
You're always the first to cry wolf when they change stuff, but you're
OK with this... monster?
I do know that yesterday or the day before, there was a change on my
Samsung phone that makes it impossible to go back to an earlier version
of an "app". *That* sucks.
On Sun, 1 Mar 2026 13:16:18 +0000, Andy Burns wrote:
When I'm in portrait mode on the tablet, and I "unfurl" the More
and Extensions sections, it does take pretty much the whole screen
(9.1" 1440x2304).
Now imagine this on a smartphone.
John C. <[email protected]> wrote:
[Thread drift:]
I do know that yesterday or the day before, there was a change on my
Samsung phone that makes it impossible to go back to an earlier version
of an "app". *That* sucks.
It it's an add-on (i.e. not pre-installed) non-paid app, you can
probably 'sideload' an older version from one of the many third-party app-stores. I mainly use(d) apkpure.com.
If this concerns one specific app, then please give the 'id=...'
identifier (or full URL) of the apps entry on the Google Play website.
On 26/03/02 06:45 AM, Frank Slootweg wrote:
John C. <[email protected]> wrote:
[Thread drift:]
I do know that yesterday or the day before, there was a change on my
Samsung phone that makes it impossible to go back to an earlier version
of an "app". *That* sucks.
It it's an add-on (i.e. not pre-installed) non-paid app, you can
probably 'sideload' an older version from one of the many third-party app-stores. I mainly use(d) apkpure.com.
If this concerns one specific app, then please give the 'id=...' identifier (or full URL) of the apps entry on the Google Play website.
No, it didn't concern one specific app. The information came from a notification when I updated Android AND Samsung things. AI says:
"Recent Android and Samsung updates (including One UI 6 and later)
strengthen security by preventing downgrades to older app versions,
often resulting in an INSTALL_FAILED_VERSION_DOWNGRADE error. This restriction is designed to stop security vulnerabilities, potential
privilege escalation, and data exfiltration. While some system apps can
be reverted to factory settings, third-party apps are generally locked
to the updated version."
(https://www.esper.io/blog/android-system-app-downgrade-vulnerability-fix).o*actually* says:
Also: __________________________________________________________________________________
Key Reasons and Limitations:
Security Restrictions: The update prevents downgrading to prevent, bugs, stability issues, and security vulnerabilities, as noted by users and
experts on Samsung Community (https://eu.community.samsung.com/t5/samsung-lounge/can-i-revert-one-ui-6-0-update/td-p/8790916)
I hope this answers your question.
John C. <[email protected]> wrote:
On 26/03/02 06:45 AM, Frank Slootweg wrote:
John C. <[email protected]> wrote:
[Thread drift:]
I do know that yesterday or the day before, there was a change on my
Samsung phone that makes it impossible to go back to an earlier version >>>> of an "app". *That* sucks.
It it's an add-on (i.e. not pre-installed) non-paid app, you can
probably 'sideload' an older version from one of the many third-party
app-stores. I mainly use(d) apkpure.com.
If this concerns one specific app, then please give the 'id=...'
identifier (or full URL) of the apps entry on the Google Play website.
No, it didn't concern one specific app. The information came from a
notification when I updated Android AND Samsung things. AI says:
Thanks. So much for 'AI'.
"Recent Android and Samsung updates (including One UI 6 and later)
strengthen security by preventing downgrades to older app versions,
often resulting in an INSTALL_FAILED_VERSION_DOWNGRADE error. This
restriction is designed to stop security vulnerabilities, potential
privilege escalation, and data exfiltration. While some system apps can
be reverted to factory settings, third-party apps are generally locked
to the updated version."
The reference you gave
(https://www.esper.io/blog/android-system-app-downgrade-vulnerability-fix).o*actually* says:
"Failure [INSTALL_FAILED_VERSION_DOWNGRADE: System app:
com.google.android.apps.wellbeing cannot be downgraded to older than
its preloaded version on the system image. Update version code 439367
is older than 452937"
So a *pre-installed* (factory supplied) app can not be downgraded to
an older version than originally came with the device. Duh!
This has nothing to do with add-on apps, i.e. the apps you installed
later.
Also:
__________________________________________________________________________________
Key Reasons and Limitations:
Security Restrictions: The update prevents downgrading to prevent, bugs,
stability issues, and security vulnerabilities, as noted by users and
experts on Samsung Community
(https://eu.community.samsung.com/t5/samsung-lounge/can-i-revert-one-ui-6-0-update/td-p/8790916)
This is about not being able to downgrade Samsung's One UI, which is
indeed true. Just like you can not downgrade Android to an earlier
version.
I have never had a problem with either, but not being able to
downgrade One UI and Android is indeed a fact of life.
It's basically the same for most OSs, including Windows. But with non-mobile OSs, you can sometimes *re-install* (not downgrade to) an
older version, which is (very) hard to 'impossible' on a monbile-OS.
[...]
I hope this answers your question.
I hope this eases your concerns! :-)
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,099 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492375:33:39 |
| Calls: | 14,106 |
| Calls today: | 2 |
| Files: | 187,124 |
| D/L today: |
1,804 files (806M bytes) |
| Messages: | 2,496,079 |
