We have to adjust MouseEvent's clientX and clientY so that they should be based on coordinate system of the parent document.
See the comment here: https://bugs.webkit.org/show_bug.cgi?id=93678#c4
My latest patch removes the dead code that was doing this incorrectly. If we implement seamless frames, then we will come back to this and we should cover this with testing.