Currently code inside the XBL directory is responsible for handling keyboard shortcut handlers defined by XBL, keyboard shortcut handlers defined by XUL <key> elements. And some global keyboard shortcut handlers defined in dom/xbl/builtin.

The majority of this code isn't XBL specific at all. I'm experimenting with ripping out the shared pieces into dom/events and just having XBL handlers extend that instead.

This should make it easier to remove support for XBL.

Here is an overview of the plan I want to follow. This bug covers part 1.

https://docs.google.com/document/d/1_Z2P5LeISwXt7JKuS9rKJkJg-ubWbMWUIMXPnbBrywg/

Most of our keyboard shortcut handling is handled by nsXBLWindowKeyHandler along
with nsXBLPrototypeHandler. With the impending removal of XBL this needs to
change.

This patch moves nsXBLWindowKeyHandler to dom/events/GlobalKeyListener and copies
nsXBLPrototypeHandler to dom/events/KeyEventHandler. Windows, text elements and
XUL <keyset> are changed to use the new copies and anything unnecessary for
those is stripped out.

XBL handler elements still remain using the existing nsXBLPrototypeHandler path.
Some of the code is ripped out there to make it compile. There is probably a
lot more that can be removed but since the whole of XBL is likely gone soon I'm
not sure it is worth cleaning that up much.

smaug: Could you check the strategy of the new directory and class names which I asked from Phabricator.

answered in ph

Backed out for Android build bustages.

Push with failure: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception&searchStr=android%2Cbuild&revision=e18ae5f66cacf06f72113830dc87ea8a5435b63b&selectedJob=265186274

Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=265186274&repo=autoland&lineNumber=27083

Backout: https://hg.mozilla.org/integration/autoland/rev/65ad92a24f8bfaccd877559118778ee3aac50ef5

https://hg.mozilla.org/mozilla-central/rev/454b9be1b613