RESOLVED FIXED 71590
[chromium] Use the security origin instead of the URL when checking notification permissions
https://bugs.webkit.org/show_bug.cgi?id=71590
Summary [chromium] Use the security origin instead of the URL when checking notificat...
Daniel Cheng
Reported 2011-11-04 15:11:44 PDT
[chromium] Use the security origin instead of the URL when checking notification permissions
Attachments
Patch (2.61 KB, patch)
2011-11-04 15:12 PDT, Daniel Cheng
no flags
Patch (5.33 KB, patch)
2011-11-04 15:53 PDT, Daniel Cheng
dcheng: review-
webkit.review.bot: commit-queue-
Daniel Cheng
Comment 1 2011-11-04 15:12:06 PDT
WebKit Review Bot
Comment 2 2011-11-04 15:14:21 PDT
Please wait for approval from fishd@chromium.org before submitting because this patch contains changes to the Chromium public API.
WebKit Review Bot
Comment 3 2011-11-04 15:17:51 PDT
Comment on attachment 113718 [details] Patch Attachment 113718 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10332103
Adam Barth
Comment 4 2011-11-04 15:23:48 PDT
Comment on attachment 113718 [details] Patch Technically fishd should review this patch. If you've updated Chromium already, you might need to update the chromium_rev in Source/WebKit/chromium/DEPS
Daniel Cheng
Comment 5 2011-11-04 15:25:29 PDT
Yep, I'm waiting for fishd and verifying that rolling the chromium DEPS in this patch will fix it.
Daniel Cheng
Comment 6 2011-11-04 15:53:14 PDT
Daniel Cheng
Comment 7 2011-11-04 15:55:55 PDT
One weird thing I noticed--it looks like WebString has a conversion operator to WTF::String (http://codesearch.google.com/codesearch#OAMlx_jo-ck/src/third_party/WebKit/Source/WebKit/chromium/public/WebString.h&exact_package=chromium&q=WebString&type=cs&l=104). However... it doesn't seem to work and I need to manually construct a WTF::String. Am I doing something wrong?
Adam Barth
Comment 8 2011-11-04 15:56:29 PDT
Comment on attachment 113723 [details] Patch LGTM, but please wait for a thumbs up from fishd before landing.
WebKit Review Bot
Comment 9 2011-11-04 16:32:47 PDT
Comment on attachment 113723 [details] Patch Attachment 113723 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10332122 New failing tests: fast/notifications/notifications-display-close-events.html fast/notifications/notifications-click-event.html fast/notifications/notifications-check-permission.html fast/notifications/notifications-rtl.html fast/notifications/notifications-no-icon.html fast/notifications/notifications-replace.html fast/notifications/notifications-with-permission.html fast/notifications/notifications-double-show.html
Daniel Cheng
Comment 10 2011-11-04 16:35:14 PDT
Comment on attachment 113723 [details] Patch R- until I figure out how to fix the tests. Oddly enough the corresponding Chrome extension tests still seem to work.
Darin Fisher (:fishd, Google)
Comment 11 2011-11-05 14:57:51 PDT
Comment on attachment 113723 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=113723&action=review > Source/WebKit/chromium/public/WebNotificationPresenter.h:63 > + virtual Permission checkPermission(const WebSecurityOrigin&) = 0; WebKit API changes LGTM
Daniel Cheng
Comment 12 2011-11-05 21:15:09 PDT
Yuta Kitamura
Comment 13 2011-11-06 02:03:44 PST
This change caused compile errors on Chromium canary builders: http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Win%20Builder/builds/15854 Could you fix them or roll out your change at your earliest convenience? (I'm on limited network connection right now and can't fix this for you.)
Daniel Cheng
Comment 14 2011-11-06 09:16:38 PST
(In reply to comment #13) > This change caused compile errors on Chromium canary builders: > http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Win%20Builder/builds/15854 > > Could you fix them or roll out your change at your earliest convenience? (I'm on limited network connection right now and can't fix this for you.) Sorry for not catching this locally. I have a Chromium-side fix ready to go, I'm waiting for the Chromium tree to re-open.
Daniel Cheng
Comment 15 2011-11-06 10:49:26 PST
Chromium r108814 should fix this. I'll clobber the Windows builder to be sure.
Yuta Kitamura
Comment 16 2011-11-06 18:51:57 PST
I confirmed the fix. Thanks!
Note You need to log in before you can comment on or make changes to this bug.