Status: Assigned Owner: [email protected] CC: [email protected], [email protected] Labels: Type-Bug Pri-3 OS-All Area-BrowserUI I18N RTL
New issue 6821 by [email protected]: Replace ScreenToClient and ClientToScreen with MapWindowPoints to make Chrome RTL-proof http://code.google.com/p/chromium/issues/detail?id=6821 <see b/682902> According to http://www.microsoft.com/globaldev/getwr/steps/WRG_mirror.mspx to take advantage of 'automatic' mirroring by Windows, we should use MapWindowPoints in place of ScreenToClient and ClientToScreen. This will make Chrome BiDi / RTL-proof down the road. From Peter: We fixed some of these but we should probably still audit the code to see if there are more of these. From Idan: It is certainly true that it is not a good practice to use ScreenToClient()/ClientToScreen(). However, the Chrome mirroring infrastructure doesn't really rely on the HWND mirroring support and therefore the fact that we do call these methods from a few places in the code is, at least as far as I can tell, harmless. Thus, the priority of this bug shouldn't be P2 since there is no impact whatsoever on the UI. We should replace the aforementioned calls with calls to MapWindowPoints() sometime in the future in order to follow the known l10n conventions. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
