Swiping between Firefox and custom tab doesn't lock PBM
Categories
(Firefox for Android :: Privacy, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | unaffected |
| firefox142 | --- | wontfix |
| firefox143 | --- | fixed |
People
(Reporter: rebecatudor273, Assigned: mavduevskiy)
References
(Blocks 1 open bug)
Details
(4 keywords, Whiteboard: [fxdroid][group2][adv-main143+])
Attachments
(1 file, 1 obsolete file)
|
2.50 MB,
video/mp4
|
Details |
Steps to reproduce
- In Setting -> Private browsing -> enable "Use screen lock to hide tabs in private browsing.
- In Settings -> Set Firefox as the default browser to open the custom tabs in Firefox.
- Open a private browsing tab and visit some site in that tab, e.g. https://example.org .
- Switch to another app that can launch custom-tabs, e.g. Gmail, and tap some link to open a custom tab.
- Swipe back to Firefox.
Expected behavior
PBM is locked and authentication is required.
Actual behavior
PBM is unlocked
| Reporter | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
What device are you using? I tested this on Firefox 141.0.1 (release downloaded from the Play Store) on my Pixel 8 using both PIN and facial recognition and I'm not able to reproduce this.
Never mind, I am able to reproduce this too.
Comment 3•1 year ago
|
||
Bug 1971361 seems related. Kind of the opposite, so maybe fixing that broke this?
| Reporter | ||
Comment 4•1 year ago
|
||
I observed this issue while working on Bug 1971361. The is can be reproduced before and after applying the patch from that ticket. So it's not related to it.
Updated•1 year ago
|
| Assignee | ||
Comment 5•1 year ago
|
||
appstate.mode is updated by DefaultBrowsingModeManager during init phase; so that a custom tab is able to rewrite the mode set by the application. Managers calculate mode based on intent correctly, the missing peace was to update the appstate as well.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
The issue was fixed with the patch added in Bug 1980721.
Comment 7•1 year ago
|
||
Are older releases affected or did this only affect 143?
| Reporter | ||
Comment 8•1 year ago
|
||
142 is affected too.
Comment 9•1 year ago
|
||
The patch landed in nightly and beta is affected.
:mavduevskiy, 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 10•1 year ago
|
||
Very late in the cycle to uplift a sec-low IMO. Feel free to nominate if you feel strongly otherwise, however.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•5 months ago
|
Description
•