Changes between Version 5 and Version 6 of Known incompatibilities between open-source WebKit and Safari


Ignore:
Timestamp:
Feb 16, 2007 8:56:25 AM (17 years ago)
Author:
ddkilzer@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Known incompatibilities between open-source WebKit and Safari

    v5 v6  
    1 Versions of Safari that were released with 10.4 (Tiger) or a 10.4.x update should work correctly with locally-built versions of WebKit in nearly all ways. Ideally there would be no incompatibilities at all, but occasionally it is necessary to introduce an incompatibility so that WebKit can evolve without amassing globs of special-case backwards-compatibility code.
     1Safari 2.0.x for Mac OS X 10.4 (Tiger) or a 10.4.x update should work correctly with locally-built versions of WebKit in nearly all ways. Ideally there would be no incompatibilities at all, but occasionally it is necessary to introduce an incompatibility so that WebKit can evolve without amassing globs of special-case backwards-compatibility code.
    22
    3 This 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.
     3This page is intended to list all of the deliberate incompatibilities between using Safari 2.0.x in Tiger 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
    55=== Forms auto-fill doesn't work ===
    66
    7 Forms 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.
     7Forms auto-fill in Safari 2.0 on Tiger 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
    99=== Clicking on links in content-editable divs loads the link ===
    1010
    11 The fix for [http://bugs.webkit.org/show_bug.cgi?id=11297 Bug 11297] required a change to Safari, thus this bug will exist in Safari in Tiger in WebKit nightlies.  See [http://bugs.webkit.org/show_bug.cgi?id=11297#c4 Bug 11297 Comment #4] for details.
     11The fix for [http://bugs.webkit.org/show_bug.cgi?id=11297 Bug 11297] required a change to future releases of Safari, thus this bug will exist in Safari 2.0.x in Tiger with WebKit nightlies.  See [http://bugs.webkit.org/show_bug.cgi?id=11297#c4 Bug 11297 Comment #4] for details.
    1212
    1313=== Editing-related context menu items don't show up ===
    1414
    15 As noted in [http://bugs.webkit.org/show_bug.cgi?id=12761#c3 Bug 12761 Comment #3], contextual menu items related to editing will not show up with Safari in Tiger when used with WebKit nightlies.
     15As noted in [http://bugs.webkit.org/show_bug.cgi?id=12761#c3 Bug 12761 Comment #3], contextual menu items related to editing will not show up with Safari 2.0.x in Tiger when used with WebKit nightlies.
    1616