Bug 73567

Summary: [chromium] add referrer policy to WebContextMenuData
Product: WebKit Reporter: jochen
Component: New BugsAssignee: jochen
Status: RESOLVED FIXED    
Severity: Normal CC: dglazkov, dpranke, fishd, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch
none
merge to r101718 none

jochen
Reported 2011-12-01 08:52:03 PST
[chromium] add referrer policy to WebContextMenuData
Attachments
Patch (2.31 KB, patch)
2011-12-01 08:54 PST, jochen 		no flags
DetailsFormatted DiffDiff
Patch (2.36 KB, patch)
2011-12-01 11:12 PST, jochen 		no flags
DetailsFormatted DiffDiff
merge to r101718 (72.62 KB, patch)
2011-12-01 16:23 PST, Dirk Pranke 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
jochen
Comment 1 2011-12-01 08:54:25 PST
Created attachment 117430 [details] Patch
jochen
Comment 2 2011-12-01 08:55:18 PST
Darin, can you please review this?
WebKit Review Bot
Comment 3 2011-12-01 08:56:59 PST
Please wait for approval from fishd@chromium.org before submitting because this patch contains changes to the Chromium public API.
WebKit Review Bot
Comment 4 2011-12-01 09:08:43 PST
Comment on attachment 117430 [details] Patch Attachment 117430 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10694637
jochen
Comment 5 2011-12-01 11:12:42 PST
Created attachment 117447 [details] Patch
WebKit Review Bot
Comment 6 2011-12-01 14:26:06 PST
Comment on attachment 117447 [details] Patch Clearing flags on attachment: 117447 Committed r101709: <http://trac.webkit.org/changeset/101709>
WebKit Review Bot
Comment 7 2011-12-01 14:26:11 PST
All reviewed patches have been landed. Closing bug.
Dirk Pranke
Comment 8 2011-12-01 16:23:21 PST
Created attachment 117516 [details] merge to r101718
Dirk Pranke
Comment 9 2011-12-01 16:32:41 PST
webkit-patch went bonkers and added my attachment to the wrong bug. Please ignore :).
Note You need to log in before you can comment on or make changes to this bug.