summaryrefslogtreecommitdiffstats
path: root/content/browser/download/drag_download_util.h
Commit message (Collapse)AuthorAgeFilesLines
* Move TabContentsDragWin to content and rename it to WebContentsDragWin.jam@chromium.org2012-03-051-7/+6
| | | | | | | BUG=98716 Review URL: https://chromiumcodereview.appspot.com/9594012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124951 0039d316-1c4b-4281-b951-d872f2087c98
* Hooked up NetLog to DownloadItem, DownloadFile, and FileStream.ahendrickson@chromium.org2012-02-091-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | The ChromeNetLog object is owned by the browser process, which has a longer lifetime than the profile and therefore than the download system. For each download, there will be one BoundNetLog (or a copy thereof) used by DownloadItem and DownloadFile, and one separate one used by FileStream. For most downloads, the path to get a NetLog pointer to the download objects (DownloadItem, DownloadFile and FileStream) is through the URL request. A BoundNetLog is created and passed in to the DownloadResourceHandler constructor, which adds it to a DownloadCreateInfo that it makes. This gets it to DownloadItem, DownloadFile/BaseFile, and FileStream. For downloads created from the history database, the path is via the DownloadService and the DownloadManager constructor. Likewise for downloads created as part of a 'Save Page As' operation, although that may change in the future with further refactoring of the 'Save Page As' code. For downloads initiated by drag & drop on Linux and Mac (but not on Windows), the FileStream needs to get a NetLog pointer from another source. In this case, it is via the ContentClient (effectively a global) and ContentBrowserClient classes. Note that FileStream has a different NetLog source than the other classes. This is the final of 4 CLs that will enable net logging for downloads. BUG=None TEST=Go to a web page with downloadable content. Open a new tab with about:net-internals. Download a file. Check the EVENTS tab of about:net-internals: there should be DOWNLOAD and FILESTREAM events. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=121050 Review URL: http://codereview.chromium.org/9296012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121195 0039d316-1c4b-4281-b951-d872f2087c98
* Back out r121050 from the trunk due to a compile failure.mark@chromium.org2012-02-081-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | http://build.chromium.org/p/chromium/builders/Win%20Aura/builds/5477/steps/compile/logs/stdio Hooked up NetLog to DownloadItem, DownloadFile, and FileStream. The ChromeNetLog object is owned by the browser process, which has a longer lifetime than the profile and therefore than the download system. For each download, there will be one BoundNetLog (or a copy thereof) used by DownloadItem and DownloadFile, and one separate one used by FileStream. For most downloads, the path to get a NetLog pointer to the download objects (DownloadItem, DownloadFile and FileStream) is through the URL request. A BoundNetLog is created and passed in to the DownloadResourceHandler constructor, which adds it to a DownloadCreateInfo that it makes. This gets it to DownloadItem, DownloadFile/BaseFile, and FileStream. For downloads created from the history database, the path is via the DownloadService and the DownloadManager constructor. Likewise for downloads created as part of a 'Save Page As' operation, although that may change in the future with further refactoring of the 'Save Page As' code. For downloads initiated by drag & drop on Linux and Mac (but not on Windows), the FileStream needs to get a NetLog pointer from another source. In this case, it is via the ContentClient (effectively a global) and ContentBrowserClient classes. Note that FileStream has a different NetLog source than the other classes. This is the final of 4 CLs that will enable net logging for downloads. BUG=None TEST=Go to a web page with downloadable content. Open a new tab with about:net-internals. Download a file. Check the EVENTS tab of about:net-internals: there should be DOWNLOAD and FILESTREAM events. Review URL: http://codereview.chromium.org/9296012 TBR=ahendrickson@chromium.org Review URL: https://chromiumcodereview.appspot.com/9361048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121073 0039d316-1c4b-4281-b951-d872f2087c98
* Hooked up NetLog to DownloadItem, DownloadFile, and FileStream.ahendrickson@chromium.org2012-02-081-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | The ChromeNetLog object is owned by the browser process, which has a longer lifetime than the profile and therefore than the download system. For each download, there will be one BoundNetLog (or a copy thereof) used by DownloadItem and DownloadFile, and one separate one used by FileStream. For most downloads, the path to get a NetLog pointer to the download objects (DownloadItem, DownloadFile and FileStream) is through the URL request. A BoundNetLog is created and passed in to the DownloadResourceHandler constructor, which adds it to a DownloadCreateInfo that it makes. This gets it to DownloadItem, DownloadFile/BaseFile, and FileStream. For downloads created from the history database, the path is via the DownloadService and the DownloadManager constructor. Likewise for downloads created as part of a 'Save Page As' operation, although that may change in the future with further refactoring of the 'Save Page As' code. For downloads initiated by drag & drop on Linux and Mac (but not on Windows), the FileStream needs to get a NetLog pointer from another source. In this case, it is via the ContentClient (effectively a global) and ContentBrowserClient classes. Note that FileStream has a different NetLog source than the other classes. This is the final of 4 CLs that will enable net logging for downloads. BUG=None TEST=Go to a web page with downloadable content. Open a new tab with about:net-internals. Download a file. Check the EVENTS tab of about:net-internals: there should be DOWNLOAD and FILESTREAM events. Review URL: http://codereview.chromium.org/9296012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@121050 0039d316-1c4b-4281-b951-d872f2087c98
* Add OVERRIDE to content/.avi@chromium.org2011-11-171-2/+2
| | | | | | | | | BUG=104314 TEST=no change Review URL: http://codereview.chromium.org/8587009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110544 0039d316-1c4b-4281-b951-d872f2087c98
* Export some unix-specific content symbols.dpranke@chromium.org2011-10-041-2/+2
| | | | | | | | | | R=jam@chromium.org BUG=90442 TEST= Review URL: http://codereview.chromium.org/8113027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@103929 0039d316-1c4b-4281-b951-d872f2087c98
* Annotate all of the functions in content that need to be exported, in ↵dpranke@chromium.org2011-09-131-4/+5
| | | | | | | | | | | | preparation for creating a content shared library. R=darin@chromium.org, jam@chromium.org, willchan@chromium.org BUG=90442 TEST=everything still compiles Review URL: http://codereview.chromium.org/7800015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100975 0039d316-1c4b-4281-b951-d872f2087c98
* content: Move drag_download_* to content.erg@google.com2011-08-241-0/+62
These are leaf nodes in moving tab_contents_view_gtk, and usage is sparse enough that I'm just moving the headers and fixing up the three places that they are included. BUG=93804 TEST=none; code move Review URL: http://codereview.chromium.org/7720014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@98073 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-23 00:40:18 +0000