Bug 104013

Summary: [WK2] URL schemes registered as local, no access, display isolated and as CORS enabled are not registered again after a web process crash
Product: WebKit Reporter: Joaquim Rocha <jrocha>
Component: WebKit2Assignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: darin, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Joaquim Rocha
Reported 2012-12-04 10:22:10 PST
Although urlSchemesRegisteredAsLocal, urlSchemesRegisteredAsNoAccess, urlSchemesRegisteredAsDisplayIsolated and urlSchemesRegisteredAsCORSEnabled are correctly dealt with in WebProcessCreationParameters and there are methods to register them in WebProcess, those are not called on initializeWebProcess so in case of e.g. a crash, when the web process is relaunched again, these schmes do not get registered. It is an easy fix and I'll upload a patch very soon.
Attachments
Patch (2.42 KB, patch)
2012-12-04 10:38 PST, Joaquim Rocha 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Joaquim Rocha
Comment 1 2012-12-04 10:38:24 PST
Created attachment 177508 [details] Patch
WebKit Review Bot
Comment 2 2012-12-05 00:27:33 PST
Comment on attachment 177508 [details] Patch Clearing flags on attachment: 177508 Committed r136650: <http://trac.webkit.org/changeset/136650>
WebKit Review Bot
Comment 3 2012-12-05 00:27:36 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.