Bug 104013 - [WK2] URL schemes registered as local, no access, display isolated and as CORS enabled are not registered again after a web process crash
Summary: [WK2] URL schemes registered as local, no access, display isolated and as COR...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-04 10:22 PST by Joaquim Rocha
Modified: 2012-12-05 00:27 PST (History)
2 users (show)

See Also:

Attachments
Patch (2.42 KB, patch)
2012-12-04 10:38 PST, Joaquim Rocha 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joaquim Rocha 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.
Comment 1 Joaquim Rocha 2012-12-04 10:38:24 PST 
Created attachment 177508 [details]
Patch
Comment 2 WebKit Review Bot 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>
Comment 3 WebKit Review Bot 2012-12-05 00:27:36 PST 
All reviewed patches have been landed.  Closing bug.