Summary: | [iOS Simulator] WebCoreNSURLSessionTest API tests BasicOperation and InvalidateEmpty failing | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> | ||||
Component: | New Bugs | Assignee: | Jer Noble <jer.noble> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | achristensen, ap, jer.noble | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | iPhone / iPad | ||||||
OS: | iOS 9.0 | ||||||
Attachments: |
|
Description
Ryan Haddad
2016-02-04 12:47:59 PST
Interesting. I'll take a look. Created attachment 270706 [details]
Patch
I also have solutions to this in https://bugs.webkit.org/show_bug.cgi?id=153900 For the meanwhile, before the more drastic change is made to +[WebView initialize], can we r+ this to get the iOS tests unblocked? If we're just trying to fix tests, I think https://bugs.webkit.org/attachment.cgi?id=270700&action=review is a better solution than adding more UIKit SPI usage. Comment on attachment 270706 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=270706&action=review > Tools/TestWebKitAPI/Tests/WebCore/WebCoreNSURLSession.mm:48 > +SOFT_LINK(UIKit, _UIApplicationLoadWebKit, void, (void), ()) If this is necessary for WebKit tests, should we do this in shared code? The fix in https://bugs.webkit.org/show_bug.cgi?id=153900 seems preferable still, but I don't know if there is some reason why we can't do initialization in WebKit. *** This bug has been marked as a duplicate of bug 153900 *** |