On Wednesday, January 25, 2012 01:31:00 PM ext Sylvain Pointeau wrote: > On Wed, Jan 25, 2012 at 1:25 PM, Simon Hausmann <[email protected]>wrote: > > On Wednesday, January 25, 2012 01:20:57 PM ext Sylvain Pointeau wrote: > > > > > AFAIK, they just want to preserve compatibility with > > > > > existing > > > > > > > > applications. WebKit2 architecture allows to expose both WebKit1 > > > > and > > > > WebKit2 APIs from single build of WebKit, so it's not a big deal > > > > to > > > > keep > > > > > > both APIs. > > > > > > Why are we then breaking the Qt API? > > > > Where is the API being broken? > > QWebElement?
The API is not being _broken_. It continues to be available in Qt 5, as well as QWebPage, QWebView and QGraphicsWebView. They work on top of the QWidget based stack. However we choose not to support these APIs with QQuickCanvas & friends, we leave that to the WebKit2 based QML WebView component. Simon _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
