3 ms·
> Why not go and submit a patch there? Because WebKit is a rendering engine, not a UI. The Safari UI wrapper is responsible for receiving those touch events an
by delinka 14y ago
> Why not go and submit a patch there?
Because WebKit is a rendering engine, not a UI. The Safari UI wrapper is responsible for receiving those touch events and properly notifying the rest of the browser code.
- batista 14y agoAh, snap. Haven't thought of that.
- saurik 14y agoMuch of this code actually is in WebKit, but Apple's form of WebKit is not open-source. Apple carefully redacts code that would provide other mobile device platforms any help against Apple's usability features, and multi-touch is one of these defended systems. Really, as WebKit is under a BSD license, Apple can thereby leach off other developer's work without having to contribute back. They have to make a token effort at releasing their modifications to WebCore (a part of WebKit that is under LGPL), but even there they release binary object files for anything remotely related to the mobile UI. (Aside: this is possible, as LGPL does let you static ally link against closed-source code as long as you provide the half-compiled binaries required to re-link a complete binary with modifications to the LGPL parts made by third parties.)