Include a few tests that test the notifications API for DRT and WTR.
<rdar://problem/12209303>
Created attachment 161542 [details] WIP Patch
Comment on attachment 161542 [details] WIP Patch Attachment 161542 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13682936 New failing tests: http/tests/notifications/show.html http/tests/notifications/request.html
Created attachment 161627 [details] Patch
Comment on attachment 161627 [details] Patch Attachment 161627 [details] did not pass win-ews (win): Output: http://queues.webkit.org/results/13716072
Created attachment 161631 [details] Patch
Comment on attachment 161631 [details] Patch Attachment 161631 [details] did not pass win-ews (win): Output: http://queues.webkit.org/results/13722064
Created attachment 161733 [details] Patch
Comment on attachment 161733 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=161733&action=review > Source/WebKit2/WebProcess/InjectedBundle/API/c/WKBundlePrivate.h:78 > +WK_EXPORT uint64_t WKBundleGetWebNotificationID(WKBundleRef bundle, JSContextRef context, JSValueRef notification); Should these methods be ForTesting?
Comment on attachment 161733 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=161733&action=review >> Source/WebKit2/WebProcess/InjectedBundle/API/c/WKBundlePrivate.h:78 >> +WK_EXPORT uint64_t WKBundleGetWebNotificationID(WKBundleRef bundle, JSContextRef context, JSValueRef notification); > > Should these methods be ForTesting? They could be. I just followed style. That whole section is just TestRunner SPI.
Committed r127299: <http://trac.webkit.org/changeset/127299>
(In reply to comment #11) > Committed r127299: <http://trac.webkit.org/changeset/127299> This caused 4 tests to start failing on Lion. Please fix soon or roll out your patch, because those 4 tests are the only thing standing between that bot and green right now.