Dragging a link doesn't use the right frame for OOPIF downloads |
|||||
Issue descriptioncontent\browser\download\drag_download_file.cc (InitiateDownload) creates a DownloadUrlParameters structure for downloading the link being dragged. This uses the main frame of the WebContents. Instead, this should use the frame that actually contained the link.
,
Feb 27 2017
No, that logic has not been changed with my update.
,
May 3 2017
Does anyone have any specific repro steps for this?
,
Oct 17 2017
,
Feb 12 2018
Mac triage: what is the concrete bug here? Should this be assigned to a specific person?
,
Feb 12 2018
It would help greatly to have a set of repro steps to see how this gets triggered. A quick glance at code search makes it appear that DragDownloadFile::Start is only called from tests at present. In any case, we would need some sort of event coordinates to determine which frame we should be using ... presumably at some point the drag events go through RenderWidgetHostInputEventRouter?
,
Mar 19 2018
Mac triage: marking assigned to wjmaclean@ |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nasko@chromium.org
, Dec 7 2016Owner: paulmeyer@chromium.org