[[PageOutline]] = How do I... = == build WebKit for Qt? == Short answer: you can't. The [https://trac.webkit.org/wiki/QtWebKit Qt port] was removed from the WebKit project in 2013. It cannot be built using WebKit trunk. Thus, WebKit contributors are unlikely to be able to answer any questions about Qt-specific issues. The Qt project maintains an [https://github.com/qtproject/qtwebkit out-of-tree branch of QtWebKit], but it is deprecated in favor of the [https://wiki.qt.io/QtWebEngine Blink-based QtWebEngine]. It is recommended you read [http://blog.kov.eti.br/2014/03/qtwebkit-is-no-more-what-now/ this blog post] for more historical context. = Releases = == When will Apple release an updated Safari with !WebKit? == Apple does not comment on future releases of Safari, their timing, nor their contents. == Will feature XXX be included in the next release of Safari? == Apple does not comment on future releases of Safari, their timing, nor their contents. == What !WebKit SVN revision is included in Safari version XXX? == This information is not publicly available. If you need to report a security concern, see [http://www.webkit.org/security/]. ---- = Nightly Builds = == Why don't WebKit Nightlies don't work on OS X El Capitan (10.11)? This should be fixed soon. In the meantime, a somewhat [WebKitNightlyElCapWorkaround onerous workaround] can be used to re-enable nightlies. == Why doesn't the version number change in the About Safari window when I'm running a nightly? == The information displayed in the About Safari window is the Safari version number, not WebKit's. It won't change unless the Safari application itself has been upgraded. == Can I replace system !WebKit with one from a nightly or local build? == Replacing the !WebKit.framework that ships with Mac OS X or any of its components with those from a locally built copy or a nightly build of !WebKit is '''HIGHLY''' discouraged. Doing so will likely leave your system unusable and cause a tear in the fabric of spacetime—so don't do it! [[BR]] There are a number of safe ways to test an application against a newer !WebKit: * If you have access to the source code, recompile it to link against the newer frameworks. It might be necessary to link against !WebCore.framework while doing this as local builds are not umbrella frameworks. * The [http://trac.webkit.org/projects/webkit/browser/trunk/Tools/Scripts/run-webkit-app run-webkit-app] script located in !Tools/Scripts allows an application to run with a locally built copy of !WebKit. * Set the DYLD_FRAMEWORK_PATH to point to the newer frameworks in your build directory. == Can !WebKit automatically update itself? == No, though the page the nightly loads when started will let you know if a newer build is available and give you a link to download it. Many people use the third party [http://web.mac.com/reinholdpenner/iWeb/Software/NightShift.html NightShift] program to update their nightly. ---- = Feedback = If you're not sure where your feedback/suggestion should go, [http://webkit.org/blog/101/back-to-basics/ this blog post] might help. If you're still not sure or have any questions, feel free to [http://webkit.org/contact.html get in touch]. == Safari should have feature XXX! == First, that's not a question :) Feedback and feature requests are always appreciated! Safari feature requests should be filed in Apple's internal bug tracker at https://bugreport.apple.com/ (free "online" account available [http://connect.apple.com/ here]) while !WebKit ones should go in our [http://bugs.webkit.org Bugzilla].[[BR]]