Issue metadata
Sign in to add a comment
|
drag of URL with a long title to desktop folder fails |
||||||||||||||||||||||||
Issue descriptionChrome Version: 63.0.3223.0 (Official Build) canary (64-bit) (cohort: 64-Bit) OS: Windows 10 What steps will reproduce the problem? (1) Visit a URL with a long title e.g. https://www.amazon.co.uk/dp/B074DVPCVJ (2) Drag the url from the omnibox to a desktop folder (3) What is the expected result? .url file is created What happens instead? no .url file is created. Please use labels and text to provide additional information. Perhaps the title is reaching the maximum filename size, and it should be cropped? For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Sep 26 2017
This issue is not specific to the omnibox, removing UI>Browser>Omnibox. For example, if I go to the following page: https://www.amazon.co.uk/s/ref=nb_sb_noss?url=search-alias%3Dlighting&field-keywords=Portable+LED+Camping+Light%2CFOGEEK I can drag most of the links on that page to the desktop and .url files are created. But if I drag the link to the page from the original report ("Portable LED Camping Light,FOGEEK [Power Bank] 5 Adjustable Modes [...]") nothing happens. My guess is that this is caused by the Windows limit on file length and when the link we try to create violates it, it fails silently. This is just a guess, but I think what's necessary is to limit the length of data.url used in Widget::RunShellDrag() or somewhere downstream of there: https://cs.chromium.org/chromium/src/ui/views/widget/widget.cc?l=784&rcl=f26dc9e577e66ad595b82e9fce4bec8861ef89cd Finally, note that I reproduced this issue in both [63.0.3223.8 (Official Build) canary (64-bit)] and [62.0.3202.29 (Official Build) beta (64-bit)] and that it's probably not a regression.
,
Sep 26 2017
Correction, I meant to say the title in the OSExchangeData objection, not the URL.
,
Sep 26 2017
Oh, brother. Correction, I meant to say "object" not "objection".
,
Oct 25 2017
jdonnelly@, looks like you already dove into this issue. It also appears the component you applied isn't being triaged. Given your past work in locating the relevant code, can you guess at appropriate people to CC on the bug?
,
Feb 14 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jdonnelly@chromium.org
, Sep 26 2017Status: Assigned (was: Untriaged)