Scrolling and zooming APIs used to operate on transformed coordinates, which is a bad idea: The UI thread might long have moved on to a different scale and scroll position so outdated pixel coordinates are of limited value. Moreover, more transformation calculations are needed than if we operate purely on document coordinates. With webkitThreadViewportAccessor() exposed, the caller has a choice between how to handle coordinates and the means to perform conversions with little effort and overhead if needed. Therefore, we should remove pixel coordinates from the public API. The patch below makes this change. Internally tracked as part of RIM PR 173292.
Created attachment 173049 [details] Patch
Comment on attachment 173049 [details] Patch This is the way we are going so r+
Comment on attachment 173049 [details] Patch Clearing flags on attachment: 173049 Committed r133914: <http://trac.webkit.org/changeset/133914>
All reviewed patches have been landed. Closing bug.