71945 2011-11-09 13:00:42 -0800 Eliminate the notion of a window coordinate system from WebCore 2011-11-29 13:16:03 -0800 1 1 1 Unclassified WebKit Platform 528+ (Nightly build) Unspecified Unspecified NEW P2 Normal --- 71954 71947 71955 72338 72397 72408 73352 1 andersca webkit-unassigned ap darin fsamuel sam simon.fraser oldest_to_newest 499278 0 andersca 2011-11-09 13:00:42 -0800 WebCore shouldn't need to know anything about window coordinates - especially not in Chromium and WebKit2 where the WebCore widget hierarchy is in a completely different process from the actual window! We should try to eliminate calls to convertToContainingWindow/convertFromContainingWindow etc and replace them with convertToRootView/convertFromRootView. The only case where window coordinates are important is in Mac WebKit1 due to the way it works with AppKit, but we should try to keep that code in the WebKit1 code. 499285 1 simon.fraser 2011-11-09 13:07:05 -0800 Awesome plan! 499443 2 darin 2011-11-09 16:11:28 -0800 Don’t window coordinates matter for things like window.screen, window.screenLeft, window.screenTop, window.innerHeight, window.outerHeight? 511046 3 andersca 2011-11-29 13:16:03 -0800 (In reply to comment #2) > Don’t window coordinates matter for things like window.screen, window.screenLeft, window.screenTop, window.innerHeight, window.outerHeight? Nope. for window.outerHeight/window.innerHeight we have a ChromeClient function to get the window rect (in screen coordinates). Nowhere in WebCore itself do we need to use window coordinates.