So for the findbar, we want the actor to be created in the context of 'web' or, in fact, anytime it is used in a regular tab. However, when loaded in an extension panel, the actor does not apply. The findbar is also used in some mochitest-chrome tests, where a browser type="content" is used, but the remoteType is empty, but we still want the actor to apply. Actors can currently be filtered based on their remote type, but I don't think the remoteType filter can handle this particular arrangement. Options: 1. Modify the remote type filter to allow more specific filtering 2. Support an additional filter type. The legacy actors check the messagemanagergroup attribute on the browser element, and can apply only to regular tabs. Nike, any thoughts here?
Bug 1610141 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
So for the findbar, we want the actor to be created in the context of 'web' or, in fact, anytime it is used in a regular tab. However, when loaded in an extension panel, the actor does not apply. The findbar is also used in some mochitest-chrome tests, where a browser type="content" is used, but the remoteType is empty, but we still want the actor to apply. Actors can currently be filtered based on their remote type, but I don't think the remoteType filter can handle this particular arrangement. Options: 1. Modify the remote type filter to allow more specific filtering 2. Support an additional filter type. The legacy actors check the messagemanagergroup attribute on the browser element, and can apply only to regular tabs. Nika, any thoughts here?