Closed
Bug 1948906
Opened 9 months ago
Closed 8 months ago
Dropping text inside the Deny Url page with the agent disconnected will not display the `Unable to connect to the DLP agent` Firefox modal window
Categories
(Firefox :: Data Loss Prevention, defect)
Tracking
()
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox135 | --- | disabled |
| firefox136 | --- | disabled |
| firefox137 | --- | affected |
People
(Reporter: atrif, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
|
1.49 MB,
image/gif
|
Details |
Found in
- 137.0a1 (2025-02-18)
window
Affected versions
- 137.0a1 (2025-02-18)
Tested platforms
- Affected platforms: Windows 10x64, Windows 11
- Unaffected platforms: Ubuntu 24, macOS
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
- DLP Agent is not running.
Steps to reproduce
- Drop random text on the yahoo.com page.
Expected result
- The
Unable to connect to the DLP agentFirefox modal is displayed (same as clipboard paste as stated here)
Actual result
- The
You're not permitted to drop this contentwindow is displayed.
Regression range
- Not a regression.
Additional notes
- Attached a screen recording.
| Reporter | ||
Updated•9 months ago
|
QA Whiteboard: [QA-2409]
Comment 1•8 months ago
|
||
This is the expected behavior for DenyUrlRegexList. The reason is that theDenyUrlRegexList` list is read from the policy and checked within the browser without having to check with the agent. Since www.yahoo.com is on the deny list, Firefox can correctly determine the action should be blocked without checking with the agent.
Bug 1929636 was slightly different in that it didn't involve the deny list. In that case, the browser was indicating the paste was blocked due to the contents of the paste, when really the content was not actually checked and the block was due to not being connected.
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•