wiki:Known incompatibilities between open-source WebKit and Safari

Version 5 (modified by ddkilzer@webkit.org, 15 years ago) (diff)

--

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.

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.

Forms auto-fill doesn't work

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.

The fix for Bug 11297 required a change to Safari, thus this bug will exist in Safari in Tiger in WebKit nightlies. See Bug 11297 Comment #4 for details.

Editing-related context menu items don't show up

As noted in Bug 12761 Comment #3, contextual menu items related to editing will not show up with Safari in Tiger when used with WebKit nightlies.