1783426 - [Windows & MacOS] Bookmark shortcut creation by dragging&dropping doesn't work for specific links

Status: NEW

(Core :: Widget: Win32, defect, P3)

Description

[Adrian Florinescu [:aflorinescu]]

Note

• This issue comes as an additional drag&drop bookmark shortcut from regressed Windows bug 1774683

Found in

• 104.0b6

Affected versions

• 105.0a1 (2022-08-05)
• 104.0b6
• 103.0.1
• 102.1.0
• 91.12.0esr

Affected platforms

• Mac 10.14.6
• Mac 11.6.8
• not affected Windows 10
• not affected Ubuntu 22.04

Steps to reproduce

1. Navigate to https://www.google.com/, left-click and hold on padlock icon in URL bar, drag to Finder/Desktop or directly on Desktop
2. Navigate to https://github.com/LibreCAD/LibreCAD, left-click and hold on padlock icon in URL bar, drag to Finder/Desktop or directly on Desktop

Expected result

• Normal bookmark shortcuts should have been created for both cases

Actual result

1. Google.com shortcut is created
2. Nothing happens

Regression range

• Doesn't seem like a regression

Additional notes

• Works on Safari
• Fails on Chrome

Comment 1

[:Gijs (he/him)]

Thanks for checking this. Are there errors in the browser console when creating the shortcut fails?

Comment 2

[Adrian Florinescu [:aflorinescu]]

(In reply to :Gijs (he/him) from comment #1)

Thanks for checking this. Are there errors in the browser console when creating the shortcut fails?

No, nothing.

Comment 3

[Neil Deakin]

The data added to the pasteboard looks correct, but the operation passed to the draggingSession endedAtPoint is 0. I'm not sure what is triggering the distinction.

Comment 4

[Simona Badau, Desktop QA]

When trying to bookmark https://github.com/LibreCAD/LibreCAD by drag and drop, on Windows 7 and Windows 10, I'm also getting the same behavior - nothing happens - reproduced with Firefox 109, Firefox 110 beta, and the latest Nightly 111.0a1.

Stephen, could this be related? Should I log a new issue for this considering I'm seeing it on Windows?
Thanks!

Comment 5

[Stephen A Pohl [:spohl]]

Let's have this bug cover both Windows and macOS unless we determine that it will require separate patches for the two platforms. I'm reassigning to Widget:Windows where it might get picked up faster.