Drag and dropping an allowed and a blocked file for upload will not upload the allowed file
Categories
(Firefox :: Data Loss Prevention, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox140 | --- | verified |
People
(Reporter: gstoll, Assigned: gstoll)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
Attachments
(7 files, 2 obsolete files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
Found in
- 138.0a1 (2025-03-17)
Affected versions
- 138.0a1 (2025-03-17)
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 running:
.\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-?\d{2}-?\d{4}.* --towarn=.*warn.* --delays=10
Steps to reproduce
- Drag and drop a blocked and an allowed file to https://codepen.io/gregstoll/full/GRYjjry.
Expected result
- The allowed file should be uploaded per 1950424#c0
Actual result
- All files are blocked.
Regression range
- Not a regression; new implementation (bug 1950424).
Additional notes
- Attached a screen recording.
- The issue reproduces as well when clipboard pasting a blocked and allowed file.
| Assignee | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
The severity field is not set for this bug.
:handyman, could you have a look please?
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Sorry, got my bugs confused.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
The new entry point analyzeBatchContentRequest() (added in a later part)
is going to want this parameter.
| Assignee | ||
Comment 5•1 year ago
|
||
This adds a nsIContentAnalysisBatchResult interface which includes the
allowedFiles that the new method returns. On the C++ side I made the
existing ContentAnalysisActionResult class implement this interface
as well, but I'm not married to this; we could make a separate class
instead.
In practice I kind of doubt that a user on Windows could actually drag
some data that has some files and some non-files, but the code should
handle this case correctly. The non-files control whether the overall
result of the nsIContentAnalysisBatchResult is eAllow or eBlock, and
the files that are allowed will get put in allowedFiles.
| Assignee | ||
Comment 6•1 year ago
|
||
The new entry point analyzeBatchContentRequest() (added in a later part)
is going to want this parameter.
| Assignee | ||
Comment 7•1 year ago
|
||
This adds a nsIContentAnalysisBatchResult interface which includes the
allowedFiles that the new method returns. On the C++ side I made the
existing ContentAnalysisActionResult class implement this interface
as well, but I'm not married to this; we could make a separate class
instead.
In practice I kind of doubt that a user on Windows could actually drag
some data that has some files and some non-files, but the code should
handle this case correctly. The non-files control whether the overall
result of the nsIContentAnalysisBatchResult is eAllow or eBlock, and
the files that are allowed will get put in allowedFiles.
| Assignee | ||
Comment 8•1 year ago
|
||
| Assignee | ||
Comment 9•1 year ago
|
||
Ideally aAllowedFilePaths would be an array of nsIFile, but unfortunately
we don't seem to be able to pass nsIFile's over IPC, so pass the paths
instead. This should be fine for Windows but may need more testing or
a better solution if/when we support Mac.
| Assignee | ||
Comment 10•1 year ago
|
||
| Assignee | ||
Comment 11•1 year ago
|
||
| Assignee | ||
Comment 12•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 13•1 year ago
|
||
Comment 14•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/55ab0d218137
https://hg.mozilla.org/mozilla-central/rev/3fee4b4f2e97
https://hg.mozilla.org/mozilla-central/rev/d65985bc1774
https://hg.mozilla.org/mozilla-central/rev/65557232a65f
https://hg.mozilla.org/mozilla-central/rev/db291af4e23d
https://hg.mozilla.org/mozilla-central/rev/d41e3c1fae52
https://hg.mozilla.org/mozilla-central/rev/f284a629b1c1
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Hello! Verified fixed with Firefox 140.0b1 on Windows 10x64. The ALLOWed file is correctly uploaded via drag and drop when a blocked and an allowed file are uploaded.
Updated•8 months ago
|
Description
•