| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | == Extensions don't work in !WebKit! / !WebKit crashes with extensions installed! == |
| | 4 | Extensions are completely unsupported with any version of Safari/!WebKit. To provide their functionality, extensions rely on private APIs and implementation details that often change and cause the extensions to break. There have been many changes to !WebKit since the currently released version and the way extensions deal with changes and errors varies greatly, with many crashing often.[[BR]] |
| | 5 | |
| | 6 | !WebKit will detect if you have any extensions installed and warn you if it comes across any. If !WebKit crashes, please remove any extensions from the following directories and see if you can reproduce the problem before [http://webkit.org/quality/reporting.html filing a bug]: |
| | 7 | |
| | 8 | {{{ |
| | 9 | ~/Library/InputManagers/ |
| | 10 | ~/Library/Application Support/SIMBL/Plugins/ |
| | 11 | ~/Library/Application Enhancers/ |
| | 12 | /Library/InputManagers/ |
| | 13 | /Library/Application Support/SIMBL/Plugins/ |
| | 14 | /Library/Application Enhancers/ |
| | 15 | }}} |
| | 16 | |
| | 17 | |
| | 18 | == When will Apple release an updated !WebKit for Tiger or Panther? == |
| | 19 | Apple doesn't comment on future products. |
| | 20 | |
| | 21 | |
| | 22 | == Why doesn't the version number change in the About Safari window when I'm running a nightly? == |
| | 23 | The info 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. |
| | 24 | |
| | 25 | |
| | 26 | == Can I replace system !WebKit with one from a nightly or local build? == |
| | 27 | Replacing the !WebKit.framework that ships with Mac OS X or any of it's components with those from a locally built copy or a nightly build of !WebKit is '''HIGHLY''' discouraged. Doing so will likely leave your system unusuable and cause a tear in the fabric of spacetime - so don't do it! [[BR]] |
| | 28 | |
| | 29 | There are a number of safe ways to test an application against a newer !WebKit: |
| | 30 | * 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. |
| | 31 | * The [http://trac.webkit.org/projects/webkit/browser/trunk/WebKitTools/Scripts/run-webkit-app run-webkit-app] script located in !WebKitTools/Scripts allows an application to run with a locally built copy of !WebKit. |
| | 32 | * Set the DYLD_FRAMEWORK_PATH to point to the newer frameworks. |
| | 33 | |
| | 34 | |
| | 35 | == Can !WebKit automatically update itself? == |
| | 36 | 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. |
| | 37 | |
| | 38 | |
| | 39 | == Safari should have a spiffy feature every other browser has! == |
| | 40 | 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]] |
| | 41 | |
| | 42 | 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 it touch]. |
| | 43 | |
