On Thu, Mar 17, 2016 at 10:54 AM, René J. V. <rjvber...@gmail.com> wrote: > David Edmundson wrote: > >> There was a thread "Policy regarding QtWebKit and QtScript" on >> kde-core-devel a while ago. >> http://kde.6490.n7.nabble.com/Policy-regarding-QtWebKit-and-QtScript-td1619988.html > > What I'm missing (as in not getting) in that discussion is the whole thing > about > (Qt)WebKit upstream. > > IIUC, WebKit was developed by Apple based on KHtml, and AFAIK WebKit is still > the basis for their Safari browser, and the sources are still available (e.g. > http://opensource.apple.com/release/os-x-10112/). > > Do I have to deduce that QtWebKit isn't "just" a Qt interface to WebKit, > maintained by the Qt Comp - because it is I don't see how security updates > could > have stopped?
WebKit integration was done through forking then integrating. It was awkward because merging upstream changes meant rebasing our work on theirs. That's why it's Chromium is better in this regard, you get to interact the upstream component without forking it, AFAIU. Aleix _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
