Changes between Version 1 and Version 2 of Known incompatibilities between open-source WebKit and Safari


Ignore:
Timestamp:
Nov 2, 2006 8:39:11 PM (17 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Known incompatibilities between open-source WebKit and Safari

    v1 v2  
    33This page is intended to list all of the deliberate incompatibilities between using a Tiger version of Safari and a locally-built version of WebKit. If you know of any other incompatibilities, then either this page needs updating or (more likely) they are unintentional bugs. Please use bugs.webkit.org to report such bugs.
    44
    5 ===  Forms auto-fill doesn't work ===
     5=== Forms auto-fill doesn't work ===
    66
    77Forms auto-fill in Safari is entirely disabled with a locally-built version of WebKit. This was necessary in order to rewrite the form control code in WebKit to not rely on using NSViews, a project that is currently underway.
    88
    9 ===  Context menu for selected text is missing three menu items ===
     9=== Context menu for selected text is missing three menu items ===
    1010
    1111The context menu for selected text on an HTML page in Tiger Safari normally includes "Search in Spotlight", "Search in Google", "Look Up in Dictionary", and "Copy". When running on locally-built WebKit, only the "Copy" item appears, preceded by two separators. This change was necessary in order to make public API that allows clients to recognize these specific context menu items.
    1212
    13 ===  Automatic proxy configuration doesn't work ===
     13=== Automatic proxy configuration doesn't work ===
    1414
    1515Safari crashes when trying to access the network if automatic proxy configuration (using a PAC file) is selected in System Preferences > Network > ''interface'' > Proxies. This is an incompatibility between the JavaScriptGlue code used by the proxy mechanism and the locally-built JavaScriptCore.