Thanks, David! I'm going to punt this one to Andrea, who knows mojo better than I do, but one comment. (Andrea, feel free to confirm / deny / expand : ))
void AutomationEventRouter::BindAutomation(Interestingly, this binds *another* interface, but this method itself is an IPC from the renderer to the RendererAutomationRegistry -- which was already bound. This means that we'll prevent binding of this new interface (which is good), but I think it'd be better to pull it a step higher and prevent binding the RendererAutomationRegistry at all (which I think happens [here](https://source.chromium.org/chromium/chromium/src/+/main:extensions/browser/api/automation_internal/automation_event_router.cc;l=348-356;drc=2f59ca9d5a2454810abc62d5a235b4347c7e90c4)).
Would that work?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Interestingly, this binds *another* interface, but this method itself is an IPC from the renderer to the RendererAutomationRegistry -- which was already bound. This means that we'll prevent binding of this new interface (which is good), but I think it'd be better to pull it a step higher and prevent binding the RendererAutomationRegistry at all (which I think happens [here](https://source.chromium.org/chromium/chromium/src/+/main:extensions/browser/api/automation_internal/automation_event_router.cc;l=348-356;drc=2f59ca9d5a2454810abc62d5a235b4347c7e90c4)).
Would that work?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |