Changes between Version 5 and Version 6 of FAQ


Ignore:
Timestamp:
Nov 17, 2015 9:06:04 AM (6 years ago)
Author:
BJ Burg
Comment:

clean up.

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v5 v6  
    11[[PageOutline]]
    22
    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]]
     3= Releases =
    54
    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]:
     5== When will Apple release an updated Safari with !WebKit? ==
     6Apple does not comment on future releases of Safari, their timing, nor their contents.
    77
    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 }}}
     8== Will feature XXX be included in the next release of Safari? ==
     9Apple does not comment on future releases of Safari, their timing, nor their contents.
     10
     11== What !WebKit SVN revision is included in Safari version XXX? ==
     12This information is not publicly available. If you need to report a security concern, see [http://www.webkit.org/security/].
    1613
    1714
    18 == When will Apple release an updated Safari with !WebKit? ==
    19 Apple doesn't comment on future products.
     15----
    2016
    2117
     18= Nightly Builds =
     19
     20== Why don't WebKit Nightlies don't work on OS X El Capitan (10.11)?
     21
     22This should be fixed soon. In the meantime, a somewhat [WebKitNightlyElCapWorkaround onerous workaround] can be used to re-enable nightlies.
     23
    2224== 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 
     25The 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.
    2526
    2627== 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 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 unusuable and cause a tear in the fabric of spacetime—so don't do it! [[BR]]
     28Replacing 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]]
    2829
    2930There are a number of safe ways to test an application against a newer !WebKit:
    3031 * 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.
    3132 * 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.
    32  * Set the DYLD_FRAMEWORK_PATH to point to the newer frameworks.
    33 
     33 * Set the DYLD_FRAMEWORK_PATH to point to the newer frameworks in your build directory.
    3434
    3535== Can !WebKit automatically update itself? ==
     
    3737
    3838
    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]]
     39----
     40
     41
     42= Feedback =
    4143
    4244If 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].
     45
     46== Safari should have feature XXX! ==
     47First, 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]]