Can't Fill via Context Menu

[Riajyuu]

This issue is a

• [ ] bug
• [x] feature
• [x] question

Please describe the current behavior, and explain why it's bad.

After unlocking a new database, I can't fill entry via context menu, but I indeed find a proper one from the toolbar button.

[subdavis]

Needs research. The current implementation doesn't run a single line of code until the popup gets opened, which feels pure and makes me happy.

It looks like contexte menu options can be injected without running any code on the page, so that's a good thing. I think we would need to do matching in the background page to make this happen though?

[edjroot]

The good news is you're not going to need to run a single line of code until the user chooses to fill the page. Matching is declarative and done on the background page.

It's also extremely easy: just set the contexts parameter of the chrome.contextMenus.create method (example). I think it's not granular enough to only be activated on password inputs, though, so it would probably be easiest to always show an option (e.g. "fill this page with Tusk") regardless of where the user clicks, and then open a separate window with the usual options (rather than injecting it on the page) for better security.