On Thu, Dec 4, 2008 at 5:03 PM, Jonas Klink (Google) <[EMAIL PROTECTED]> wrote: > Agreed. The generated MSAA focus events need to come with a child id, to > uniquely identify the view that is receiving focus. As part of the original > design, I chose to piggyback on the already existing ViewID enums, rather > than creating an extra, redundant accessibility ID. However, if we feel > strongly that the ViewIDs should go away, it would certainly be easy to add > another ID system instead.
It's fine for browser to depend on views (it already does extensively). Think of views as the base SDK, much like we depend on ICU etc. Typically we resolve these issues by allowing the provision of a delegate via an interface that the views component provides which code in the browser implements. e.g. the BrowserView would implement some interface provided by views. This code would locate the LocationBarView etc. It's easy for the BrowserView to do this since it owns or has quick access to all of these objects. -Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
