Thank you.
That helps more than you’d think — it goes straight into what we fix next.
There is a real split here, and it is not you. A shortcut an extension declares in
its own manifest can come back unbound — Chrome reports no error and
commands.getAll() simply returns an empty string, so the extension cannot tell that
apart from a user who never pressed the key. No extension is allowed to assign a key on your behalf.
We wrote up what that looks like from the
inside.
The per-site shortcuts this extension adds are recorded on its own options page instead, which is a different screen from Chrome’s. The documentation starts at the four things a shortcut is made of.
Nothing about you was sent. Only the reason you picked was counted.