![]() ![]() Instead this patch makes us skip the message manager in the case that we're already running in the main process. ![]() Bug 1200742 means we can't change that right now. The code the install paths use to send the messages all find the outer browser because the inner browser doesn't have a message manager. In this case we should be doing the security checks against the inner browser and notifying UI about the outer browser so the doorhangers are parented correctly. The problem is that the AMO discovery pane runs in a inside the add-ons manager which is itself running inside a. Splinter Review The messages to chrome to start add-on installs all go through the content frame message manager and we use that to determine which browser triggered the install and so which browser to use for security checks and which tab to notify the UI about.
0 Comments
Leave a Reply. |