Bug 133015 – Need a way to get a WKPageRef from a WKWebView

• Status: RESOLVED
• Resolution: WONTFIX
• Component: WebKit2

[David Farler]

PlatformWebView in WebKitTestRunner has public WKPageRef page() but WKWebView doesn't currently have API to provide this.

[David Kilzer (:ddkilzer)]

Created attachment 231634 [details]
Patch v1

I'm sure there are layer violations (like returning a C API struct from an Objective-C class), but I'm assuming we want this to move off the deprecated WKView class first.

[Benjamin Poulain]

Comment on attachment 231634 [details]
Patch v1

Cool!

[WebKit Commit Bot]

Comment on attachment 231634 [details]
Patch v1

Clearing flags on attachment: 231634

Committed r169001: <http://trac.webkit.org/changeset/169001>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Sam Weinig]

I'm worried about why this is being done.  If the idea is to use WKPageRef to set up the needed clients in WKTR, that won't work, and we will really need to add an abstraction so the objective-c API can be used there.

[Benjamin Poulain]

(In reply to comment #5)
> I'm worried about why this is being done.  If the idea is to use WKPageRef to set up the needed clients in WKTR, that won't work, and we will really need to add an abstraction so the objective-c API can be used there.

WKTR will need it to send events and some internal testing stuff.

It looks like it also setup the clients in TestController::createOtherPage(). Moving away from that is gonna suck, the C API was awesome to setup cross-port tests.

[Anders Carlsson]

Yeah, this patch is wrong. I'm going to roll it out.

[Anders Carlsson]

It should not be possible to get at the C SPI from the modern API. We're trying to get rid of the modern API.

[WebKit Commit Bot]

Re-opened since this is blocked by bug 133050

[Benjamin Poulain]

(In reply to comment #7)
> Yeah, this patch is wrong. I'm going to roll it out.

Anders, you created this situation in the first place. Any chance you could fix testing?

[Anders Carlsson]

(In reply to comment #10)
> (In reply to comment #7)
> > Yeah, this patch is wrong. I'm going to roll it out.
> 
> Anders, you created this situation in the first place. Any chance you could fix testing?

Sam is interested in fixing it.

In any case, I'm going to WONTFIX this since we're never going to expose the old SPI from the new API.

[Benjamin Poulain]

(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #7)
> > > Yeah, this patch is wrong. I'm going to roll it out.
> > 
> > Anders, you created this situation in the first place. Any chance you could fix testing?
> 
> Sam is interested in fixing it.
> 
> In any case, I'm going to WONTFIX this since we're never going to expose the old SPI from the new API.

I really don't care how we expose the internals. I just want WKView to get out of the way and be able to run certain tests.