Closed
Bug 1905282
Opened 2 years ago
Closed 2 years ago
Increase update time when updating Firefox while a DLP request is in progress or while the warning dialog is displayed
Categories
(Firefox :: Data Loss Prevention, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1901197
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox127 | --- | disabled |
| firefox128 | --- | disabled |
| firefox129 | --- | verified |
People
(Reporter: atrif, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
2.46 MB,
image/gif
|
Details |
Found in
- 129.0a1 (2024-06-25)
Affected versions
- 129.0a1 (2024-06-25)
Tested platforms
- Affected platforms: Windows 10x64, Windows 11
- Unaffected platforms: macOS 13, Ubuntu
Preconditions
- Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view
- Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json
- run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.\d{3}-?\d{2}-?\d{4}. --towarn=.warn. --delays=10
Steps to reproduce
- Download a previous nightly build.
- Paste "warning text" inside Wikipedia page and restart to update Firefox while the scan is in progress or when the warning dialog is displayed.
Expected result
- Firefox is restarted and updated almost instantly.
Actual result
- Firefox is restarted and updated only after ~1min due to Firefox processes not being closed.
Regression range
- Not a regression. New feature.
Additional notes
- Attached a screen recording.
- This also reproduces with Scan in progress dialog and does not reproduce with blocked dialog.
- This also reproduces when updating Firefox from the App Menu notification, but no visual indicator is displayed (no About Firefox window), but the update performs successfully.
- This may be a duplicate of bug 1901197, please close it if necessary.
Comment 1•2 years ago
|
||
This is (as mentioned) almost certainly the same as bug 1901197, but I'll leave it open for now to ensure that the fix to that fixes this issue.
| Reporter | ||
Comment 2•2 years ago
|
||
It seems that this is fixed after bug 1901197 on Windows 10x64 and Windows 11. Marking it as a duplicate.
You need to log in
before you can comment on or make changes to this bug.
Description
•