Can no longer cold start Android Firefox in private browsing mode by default like desktop from the app drawer or dock
Categories
(Firefox for Android :: Homepage, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox140 | --- | unaffected |
| firefox141 | --- | wontfix |
| firefox142 | --- | verified |
| firefox143 | --- | verified |
| firefox144 | --- | verified |
People
(Reporter: ke5trel, Assigned: gl)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid] [group5])
Attachments
(4 files)
STR:
- Open Android Nightly 141.0a1.
- Open a private tab.
- Close app and swipe it away from recents.
- Open Nightly from the app drawer with a single tap.
Expected:
App always starts in private tab like desktop with "Always use private browsing mode" enabled.
Actual:
App always starts in non-private tab.
Workarounds:
- Tap private button on homepage every time app is started.
- Use "New private tab" app context menu.
Requires long-pressing app icon, extra tap to start app. - "Add private browsing shortcut" to home screen.
Can only be accessed from the home screen, cannot use app drawer. User may not want shortcuts on home screen and prefer to use the app drawer which is searchable. Icon uses purple mask with only a small Firefox badge making it less recognizable. - Use Firefox Focus.
Cannot use extensions, limited customization and no Nightly branch.
This change makes it significantly more cumbersome for users that always want to use private browsing. It is now only possible from the shortcut on the home screen which sacrifices icon recognition, app drawer accessibility and searchability. Users unwilling to make those sacrifices now have to manually switch to private tab every app launch.
Regression window:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=87e010ebac62c5bed9a41c64e63df5be347f65e6&tochange=b03555008151d6d19fca7e8986f4c206074e7a82
Regressed by Bug 1968048.
| Comment hidden (obsolete) |
Comment 2•1 year ago
|
||
Gela, could you set a priority and severity to this bug? Thanks
Another workaround:
5. Add the search widget to the home screen and enable "Open links in a private tab" setting. This can be shrunk down to a single square where it shows the more recognizable Firefox logo (albeit at a reduced size) but of course this only works from the home screen and cannot be moved into the dock.
Workarounds #1 and #2 require a manual action that the user may forget and end up using a non-private tab by accident, resulting in leaks.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Comment hidden (metoo) |
| Comment hidden (metoo) |
Every time there's a change like this I kinda brace myself for coming to bugzilla and finding "that's intentional, get over it" - I realize now that in bug 1968048 that intentional is essentially the case here.
This was seemingly changed to align with iOS and work around another issue, and I'm just an end user who got their workflow messed up overnight here, but honestly I considered the behavior on iOS a strange nuisance too; it was just a copy of Safari's behavior, on the platform where FF was forced to embed Safari's engine anyway, so I figured it was mandatory or aligning with the platform expectations. The platforms are different and I think it's okay to align with different user expectations on the two.
I've already slipped up because private-at-startup is gone, and it's only been a few hours. Adding the "private shortcut" and replacing my Firefox icon with that always starts a new tab on tap, rather than returning to the running app like the base app icon does. Staying in private with the choice to step out to normal has been hugely helpful for several years now as a better Focus with extensions, inbound bookmark sync, and outbound sent tabs.
| Comment hidden (advocacy) |
Gabriel, it isn't clear why you've kept this bug open when it seems to be the new expected behavior, as per Bug 1968048.
Are you considering reverting this change?
| Reporter | ||
Comment 11•1 year ago
|
||
This bug is not about reverting Bug 1968048 but ensuring that users continue to have a way to start in private browsing by default like desktop without having to use a shortcut on the home screen.
Workaround #1 is obsolete now that the private toggle button has been removed from the homepage (Bug 1974066). New method requires going through the tabs tray which takes two extra taps or a long-press (Bug 1976279).
Comment 13•1 year ago
|
||
On some Android devices there is NO ability to add the Private Browsing link from the desktop in Android
| Comment hidden (advocacy) |
Comment 15•1 year ago
|
||
If this is an intended feature, could we get optional setting to always start in private mode if we close the app in private mode?
| Comment hidden (advocacy) |
| Comment hidden (metoo) |
| Reporter | ||
Comment 23•1 year ago
|
||
(In reply to Nigel from comment #13)
On some Android devices there is NO ability to add the Private Browsing link from the desktop in Android
Note that you may need to grant an app permission to allow Home screen shortcuts on Xiaomi devices (Bug 1808892).
Comment 24•1 year ago
|
||
(In reply to Kestrel from comment #23)
(In reply to Nigel from comment #13)
On some Android devices there is NO ability to add the Private Browsing link from the desktop in Android
Note that you may need to grant an app permission to allow Home screen shortcuts on Xiaomi devices (Bug 1808892).
Thanks, but on my device and it's launcher, it's not something that a user is able to do.
My workaround for the serious defect is to set a different colour wallpaper for the non private browsing, and as soon as Firefox launches then switch it to private browsing.
However given the serious defect, there is no workaround to launch a Web link from say an email and have it launch the link and Firefox in private mode because of this fault. I believe that this bug is at least a P2 with a s2 severity. With the current priority it could be over a year before the fault is fixed!
| Reporter | ||
Comment 25•1 year ago
|
||
(In reply to Nigel from comment #24)
on my device and it's launcher, it's not something that a user is able to do.
What device/launcher specifically?
launch a Web link from say an email and have it launch the link and Firefox in private mode
This works for me with the "Open links in a private tab" setting enabled.
Comment 26•1 year ago
•
|
||
(In reply to Kestrel from comment #25)
(In reply to Nigel from comment #24)
on my device and it's launcher, it's not something that a user is able to do.
What device/launcher specifically?
Its the FX Launcher by Droidlogic used on an Amlogic box - I possibly could create a link manually but its too much work to do. Having Firefox remember to launch in Private Mode was something that I relied on. To meet the "Apple" way is not an excuse to remove something.
launch a Web link from say an email and have it launch the link and Firefox in private mode
This works for me with the "Open links in a private tab" setting enabled.
Ah - didn't have this enabled on one of my devices - my bad
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 27•1 year ago
|
||
| Assignee | ||
Comment 28•1 year ago
|
||
Revert changes from the following:
- https://bugzilla.mozilla.org/show_bug.cgi?id=1968048
- https://bugzilla.mozilla.org/show_bug.cgi?id=1972361
- https://bugzilla.mozilla.org/show_bug.cgi?id=1973324
Original Revision: https://phabricator.services.mozilla.com/D260498
Updated•1 year ago
|
Comment 29•1 year ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: Private browsing mode would not be persisted upon application restart for users. The prior changes was to always start on Normal Browsing mode on application restart, which affected user's experience where their private browsing mode was persisted upon application restart as long as they didn't leave it.
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Ensure that the last known browsing mode is persisted upon application restart, switches and relaunch.
- Risk associated with taking this patch: Low
- Explanation of risk level: This is reverting changes that have been well covered by UI and unit tests. The logic changes to restore the last known browsing mode is a simple one line change.
- String changes made/needed: No
- Is Android affected?: no
Comment 30•1 year ago
|
||
Updated•1 year ago
|
Comment 31•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 33•1 year ago
|
||
Comment 34•1 year ago
|
||
Comment on attachment 9506075 [details]
Bug 1973769 - Persist last known browsing mode on application restart
We are already in Rc week and out of betas. I moved the request to release and will take it in the next dot release or in the case of a re-spin
Comment 35•1 year ago
|
||
The patch landed in nightly and beta is affected.
:gl, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox142towontfix.
For more information, please visit BugBot documentation.
Comment 36•1 year ago
•
|
||
This is partially fixed:
- when the user closes the app in private mode and re-opens it from the icon, the private mode persists;
- but when the user closes the app in private mode and reopens it through the widget, the normal mode is opened, not the private.
Tested on the Firefox for Android nightly 144.0a1 from 8/19 from Play Store, with a Pixel 6 (Android 16), and a Samsung Galaxy Tab S9 Ultra (Android 15).
@Gela, should I file a new bug for the widget?
| Assignee | ||
Comment 37•1 year ago
|
||
(In reply to Mira Lobontiu (Android QA) from comment #36)
This is partially fixed:
- but when the user closes the app in private mode and reopens it through the widget, the normal mode is opened, not the private.
@Gela, should I file a new bug for the widget?
Yes, let's file a bug for this. I am curious which widget you are referring to and could you test a 140 build to see if this use case that was the expected behaviour? I am trying to confirm whether or not this was regressed by Bug 1968048.
Comment 38•1 year ago
|
||
Gabriel, I filed Bug 1984686 for the widget issue.
Reproducible also on release 140.0.
| Reporter | ||
Comment 39•1 year ago
|
||
This is the previous expected behavior, the search widget is an external intent, so it only opens private when "Open links in a private tab" is enabled in settings.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 40•1 year ago
|
||
| uplift | ||
Comment 41•1 year ago
|
||
Comment 42•1 year ago
|
||
Verified as fixed on Fenix RC 142.0.1 with Poco M4 Pro (Android 12) and Samsung S24 Ultra (Android 15).
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Description
•