1927131 - Blocked dialog displayed in Google Docs / OneDrive docs after canceling an ongoing scan

Status: ASSIGNED

(Firefox :: Data Loss Prevention, defect)

Description

[Bianca Hidecuti, Desktop Test Engineering [:bhidecuti]]

Attachment: video showing the issue

Found in

• 133.0a1 (2024-10-24)

Affected versions

• 133.0a1

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

Tested platforms

• Affected platforms: Windows 10/11
• Unaffected platforms: macOS, Ubuntu

Steps to reproduce

1. Go to https://drive.google.com/drive/home and open a Google Doc
2. Copy any random text and paste it inside the gdoc
3. Press the “Cancel” button from the “Scan in progress” dialog and observe the behavior

Expected result

• The scan is canceled and no other dialogs are displayed

Actual result

• “You’re not permitted to pasted this content” dialog is displayed

Regression range

• Mozzregression points to bug 1915351

Additional notes

• See the attached video
• Also reproducing for One Drive Documents

Comment 1

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

: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.

Comment 2

[Donal Meehan [:dmeehan]]

Setting Fx133 to fixed since the regressor was backed out
https://bugzilla.mozilla.org/show_bug.cgi?id=1915351#c23

Comment 3

[Greg Stoll :gstoll]

Note that this doesn't reproduce on Wikipedia. My guess is that this has something to do with the fact that Google Docs does multiple calls to get the clipboard contents (although I thought I addressed this in bug 1915351...)

Comment 4

[Greg Stoll :gstoll]

With my testing this should be fixed by bug 1918027. I'll leave this open until then.