FWIW, it looks like changes to lock down tabs.executeScript and content scripts were originally considered[0], but I agree that tabs.executeScript not requiring

FWIW, it looks like changes to lock down tabs.executeScript and content scripts were originally considered[0], but I agree that tabs.executeScript not requiring a declared permission is a giant issue. Thanks for this discussion btw, you introduced me to a bunch of quirks in the chrome apis I wasn't aware of. [0]: https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit#heading=h.icj5clwxt3mw https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3Nzz...