Open Bug 1936530 Opened 2 months ago Updated 5 days ago

The cancel button needs to be pressed two times to stop an ongoing drag-and-drop scan

Categories

(Firefox :: Data Loss Prevention, defect)

Desktop
Windows
defect

Tracking

()

Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox133 --- unaffected
firefox134 --- disabled
firefox135 --- disabled
firefox136 --- disabled

People

(Reporter: atrif, Unassigned)

References

(Blocks 2 open bugs, Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Attached image drag_drop_1.gif

Found in

  • 135.0a1 (2024-12-10)

Affected versions

  • 135.0a1 (2024-12-10)
  • 134.0b8

Tested platforms

  • Affected platforms: Windows 11, Windows 10
  • Unaffected platforms:macOS 12, 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
  • DLP Agent is running: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-?\d{2}-?\d{4}.* --towarn=.*warn.* --delays=10

Steps to reproduce

  1. Drag and drop some text to a Wikipedia window.
  2. Press the Cancel button while the scan is in progress.

Expected result

  • The scan is canceled.

Actual result

  • The scan continues.

Regression range

Additional notes

  • Attached a screen recording.

:gstoll, since you are the author of the regressor, bug 1915351, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(gstoll)
Flags: needinfo?(gstoll)

I believe that, before bug 1915351, this was only showing the busy dialog for the first scan (there are two). So this really never worked right. Bug 1928064 (with Bug 1936020) is expected to fix this by discarding the dialogs for any requests with the same user_action_id as the one being canceled. So we think this will turn out to be a dupe.

See Also: → 1936020

The severity field is not set for this bug.
:handyman, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(davidp99)
Severity: -- → S4
Flags: needinfo?(davidp99)

Confirmed that bug 1936020 will fix this.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: