The suggested filename in a@download (added in https://bugs.webkit.org/show_bug.cgi?id=64580) is not yet used in any platform. With this patch, the suggested filename is sent to the chromium client.
Created attachment 102000 [details] patch Not ready for review yet; the parent CLs need to go in first: https://bugs.webkit.org/show_bug.cgi?id=64580 http://codereview.chromium.org/7484061/
One comment about naming. In WebKit, "suggested file name" is what comes from the network loader, which builds it from data in Content-Disposition and Content-Type headers. Perhaps a different name can be used here to reduce confusion.
I like the use of suggestedName here. It makes this variable nicely self-documenting. "Start a download of this URL with this suggested name." I think it is good that it correlate to the C-D header too. Alexey, I'm not sure why you find this confusing.
Comment on attachment 102000 [details] patch Requesting cq? since the parent patch has landed.
(In reply to comment #4) > (From update of attachment 102000 [details]) > Requesting cq? since the parent patch has landed. Actually, that revision (r91797) probably needs to get rolled into the chromium tree first. I will ping here when that happens.
(In reply to comment #5) > (In reply to comment #4) > > (From update of attachment 102000 [details] [details]) > > Requesting cq? since the parent patch has landed. > > Actually, that revision (r91797) probably needs to get rolled into the chromium tree first. I will ping here when that happens. r91797 has been rolled into chromium trunk. cq?
Comment on attachment 102000 [details] patch Clearing flags on attachment: 102000 Committed r91847: <http://trac.webkit.org/changeset/91847>
All reviewed patches have been landed. Closing bug.