Bug 143581 - Expose WKWebView's _didRelaunchProcess and _killWebContentProcess on Mac
Summary: Expose WKWebView's _didRelaunchProcess and _killWebContentProcess on Mac
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Tim Horton
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-09 15:00 PDT by Tim Horton
Modified: 2015-07-09 19:57 PDT (History)
3 users (show)

See Also:

Attachments
Patch (2.80 KB, patch)
2015-04-09 15:01 PDT, Tim Horton 		andersca: review-
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 Tim Horton 2015-04-09 15:00:56 PDT 
Expose WKWebView's _didRelaunchProcess and _killWebContentProcess on Mac
Comment 1 Tim Horton 2015-04-09 15:01:22 PDT 
Created attachment 250471 [details]
Patch
Comment 2 Anders Carlsson 2015-04-09 16:06:22 PDT 
(In reply to comment #0)
> Expose WKWebView's _didRelaunchProcess and _killWebContentProcess on Mac

Why is this needed?

I think we should try to rename _killWebContentProcess to _terminateWebContentProcess.
Comment 3 Tim Horton 2015-04-09 16:09:12 PDT 
(In reply to comment #2)
> (In reply to comment #0)
> > Expose WKWebView's _didRelaunchProcess and _killWebContentProcess on Mac
> 
> Why is this needed?

Exposing it on Mac for MiniBrowser.

> I think we should try to rename _killWebContentProcess to
> _terminateWebContentProcess.

I think that is feasible, there is only one existing client that I'm aware of.