Re:Ask HN: What would you want in an ideal web browser?
by rhaps0dy on Monday August 17, 2015 @05:26AM
(#10072011)
Correct me if I'm wrong. Isn't this webkit?
[ Parent
| on HN ]
Re:Ask HN: What would you want in an ideal web browser?
by kenOfYugen on Monday August 17, 2015 @05:42AM
(#10072064)
Isn't WebKit the rendering engine itself?
The "ideal" core I was talking about should be able to use WebKit as a rendering engine.
Re:Ask HN: What would you want in an ideal web browser?
by panic on Monday August 17, 2015 @06:07AM
(#10072132)
If no 'browsing' features are included, isn't what you're left with the rendering engine itself?
It seems like WebKit's WKWebView (or WebKitWebView on gtk, or ewk_view on efl) is pretty much what you're asking for.
Edit: WKView should be WKWebView, sorry
Re:Ask HN: What would you want in an ideal web browser?
by kenOfYugen on Monday August 17, 2015 @06:30AM
(#10072193)
By no "browsing features" I mean something closer to a headless browser. Just a library. Is that what WKView is about?
Re:Ask HN: What would you want in an ideal web browser?
by panic on Monday August 17, 2015 @06:37AM
(#10072216)
Yeah, it provides all the features of a browser without the UI for them. You embed the WKWebView (not WKView, I mistyped) in your browser app and call methods on it to load URLs, go back and forward, and so on.