Hi there, We still are going to ship Qt WebKit1 API as part of the Qt5 module QtWebKitWidgets (I am not sure the name is final though) so it is a good idea to upstream I would say. Even things which are related to Qt4 only as the WebKit1 part should, to my knowledge, still work with Qt4, and who knows whether the community (or say Digia) wants to release a new version of QtWebKit for Qt4.
Just my point of view Kenneth On Sat, Mar 31, 2012 at 1:57 AM, Girish Ramakrishnan <[email protected]> wrote: > Hi QtWebKit team, > What's the best way to deal with patches to QtWebKit1/qt4 (for > example, http://codereview.qt-project.org/#change,21292) ? > > Is the strategy still to get it all upstream? Since, I assume, there > is QtWebKit 2.3 planned how will this patch end up in Qt? (Is the > answer that it won't ever end up in Qt4?) > > If the answer is to get it all upstream - would you agree that the > sanity bot should complain when anyone tries to commit to > src/3rdparty/webkit ? > > Thanks, > Girish > _______________________________________________ > webkit-qt mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt -- Kenneth Rohde Christiansen Senior Engineer Nokia Mobile Phones, Browser / WebKit team Phone +45 4093 0598 / E-mail kenneth at webkit.org http://codeposts.blogspot.com ﹆﹆﹆ _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
