Kalle Korhonen

Poked around a little bit and asked about it at #firefox IRC channel: > 10:19 kaosko2 Components.interfaces.nsIDOMKeyEvent is gone in FF 60. seems like KeyboardEvent is the replacement. how I...

Perhaps convertQTKeyCode should simply accept window or the KeyboardEvent as a parameter, made a quick hack to validate that would work. All the calls to it are in webpage.js so...

Like I said, that was just a total hack. I basically made _c_ a var and passed window to the function: ``` function convertQTKeyCode(QTKeyCode, window){ c = window.top.KeyboardEvent; ``` That's...

At least #694 and #707 need to be resolved first.

Not quite enough just switch to newChannel2 and provide null for the rest of the arguments (even though this post seems to suggest so: https://stackoverflow.com/questions/3772788/how-to-load-file-from-inside-firefox-plugin). Perhaps need to use newChannelFromURI2...

I don't see how you could monkeypatch ActorManagerChild (see the second issue) because the error happens as soon as you try to import it `Cu.import("resource://gre/modules/ActorManagerChild.jsm");`

Slimer.js still works great for what it does, it's just that you can't use FF newer than 62 with it. If you are using Debian/Ubuntu, you can easily get Firefox...

Well a bit more than on optimization I guess. It's still going to do a redirect and expects a potential function to return a landing-uri. And on error, it just...

Or even _without_ a redirect. But yes, of course.

Appreciated, for example https://zellwk.com/blog/publish-to-npm/. Looks like litegl was published from a forked repo (https://github.com/julio-pixelements/litegl), may need to reserve different names.