Bug 202557

Summary: Stop sending list of display-isolated schemes to NetworkProcess
Product: WebKit Reporter: Alex Christensen <achristensen>
Component: New BugsAssignee: Alex Christensen <achristensen>
Status: RESOLVED FIXED    
Severity: Normal CC: webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch youennf: review+

Alex Christensen
Reported 2019-10-03 18:45:12 PDT
Stop sending list of display-isolated schemes to NetworkProcess
Attachments
Patch (9.98 KB, patch)
2019-10-03 18:47 PDT, Alex Christensen 		youennf: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Alex Christensen
Comment 1 2019-10-03 18:47:35 PDT
Created attachment 380180 [details] Patch
youenn fablet
Comment 2 2019-10-04 07:44:49 PDT
We would go from N IPC messages to N-1 IPC messages. Is the issue efficiency? Currently, we can use SecurityOrigin without any behavioural difference in web process and network process, which is nice. At some point, we might want network process to be able to handle navigation redirections, which would then end-up making use of the canDisplay check.
Alex Christensen
Comment 3 2019-10-04 08:29:53 PDT
The issue is the network-process-global dependency on the process pool, which I am trying to break. If we start using canDisplay in the network process, we will need to add an optional parameter of a non-global list of schemes to use, which is what I'm about to do with the other schemes in the SchemeRegistry that are used in the NetworkProcess.
Alex Christensen
Comment 4 2019-10-04 09:00:30 PDT
See https://bugs.webkit.org/show_bug.cgi?id=202586
Alex Christensen
Comment 5 2019-10-04 12:33:11 PDT
http://trac.webkit.org/r250739
Radar WebKit Bug Importer
Comment 6 2019-10-04 12:34:17 PDT
<rdar://problem/55991532>
Note You need to log in before you can comment on or make changes to this bug.