This always fails with Webextensions support. The simpler solutions just take an existing webengine-component from gtk or Qt and put a browser around it, but th

This always fails with Webextensions support. The simpler solutions just take an existing webengine-component from gtk or Qt and put a browser around it, but this fails with more complex features which are naturally not part of the webengine. I'm curious why nobody takes directly chromium or firefox and just integrates trydactyl to get first-class-support. The major-problem with alternative keybindings is the context they run with. Extensions run inside the page-scope, and thus are only available after the page loaded. Integrating them at app-scope (which mozilla promised to deliver around 4 years ago already), would basically solve most problems instantly.