[Tom]

You got it, Dave.

WebKit is a no-frills browser which is extended to build OmniWeb or Safari. The extension occurs at the level of coding and compiling, so we end users can't mix and match on our own.

Sneaky peeks will have problems. The problem can be in either WebKit or in the code Omni adds to extend WebKit. If an OmniWeb problem also appears in WebKit, then the issue is with WebKit code and should be reported to and fixed by Apple. If it appears only in OW then it is probably in the code Omni added onto WebKit, and thus something for Omni coders to fix.

WebKit development is ongoing. For stability and sanity, OmniWeb is based on one fairly recent WebKit code version. The corresponding WebKit compiled application, or something very near it, is what they recommend for testing to see if sneaky peek bugs are in WebKit or Omni code. If you find a bug and determine that it is in the WebKit used as basis for OmniWeb, you can then check against a more recent WebKit Nightly release to see if Apple has corrected it.

At first I was confused, but now I'm pretty sure this is how it works.

Tom