Currently we have a handful of renderer -> browser IPC messages that contain gfx::NativeViewIds:
ViewHostMsg_GetWindowRect ViewHostMsg_GetScreenInfo ViewHostMsg_GetRootWindowRect ViewHostMsg_GetRootWindowResizerRect ViewHostMsg_ScriptedPrint These make me sad because the render could ask about random NativeViewIds (HWNDs) that have nothing to do with that renderer. There are two approaches we can use to correct these infelicities: 1) Change these message to avoid sending NativeViewIds. This seems possible, but some unknown amount of work. 2) Add more state to RendererSecurityPolicy that tracks which NativeViewIds each renderer is permitted to interrogate. I'm inclined to go with (2), but I wanted to check in with Mac / Linux folks to make sure this makes sense for those platforms too. Thoughts? Adam --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
