1918582 - With content analysis on, dropping onto an object with no defined drop handler still does CA check

Status: NEW

(Firefox :: Data Loss Prevention, defect)

Description

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: load_time_drop.gif

Found in

• 132.0a1

Affected versions

• 132.0a1 (2024-09-12)

Tested platforms

• Affected platforms: Windows 11, Windows 10
• Unaffected platforms:macOS 12, Ubuntu 22

Preconditoins

• 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

1. Open the Wikipedia page.
2. Open a new window and load Wikipedia.
3. Drop a link inside the page contents of the first window.

Expected result

• After the scan the page is loaded.

Actual result

• After the scan the page is not loaded only after some time.

Regression range

• This probably happens after bug 1910452. I will set it as the regressor. Please let us know if this may be not correct.

Additional notes

• Attached a screen recording.
• This also happens when dropping text inside a text box.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1910452

:handyman, since you are the author of the regressor, bug 1910452, could you take a look?

For more information, please visit BugBot documentation.

Comment 2

[Greg Stoll :gstoll]

This might be another symptom of bug 1917334 (I bet dropping a link drops an HTML part and a plain text part)

Comment 3

[David Parks [:handyman]]

There are two issues illuminated here:

1. Dropping the text is just bug 1917334 -- the text content has two parts that are submitted to CA, but only the first one gets a dialog, so the second one is still running when interactivity returns, and the user won't see the result until all scans are done.
2. Dropping the link is a known but not yet filed issue, so we can use this bug. Dropping something in a place where there is no drop handler, so the default drop behavior happens, should not inspire a CA check, but it currently does. This won't be too easy to fix since we need to check the event targets in content (the target chain of elements, actually) for the relevant registered callbacks.

So this bug should be considered a way to demonstrate problem #2.