Ghjuvan Lacambre

>what if someone has two different Firefoxes running at the same time? Wouldn't that detect the wrong lock? No, because (on linux at least) we check the arguments that were...

Probably the `:jumpnext`/`:jumpprev` code restoring the position. I guess we should save the current position before duplicating the tab.

I remember being able to reproduce this bug but on my current machine (Firefox 73.0.1, linux, tridactyl 1.17.1pre3631-e4926ad) I can't.

On FF74+1.17.1pre3666-2f02f3e tabduplicate duplicates the tab and navigates to the homepage. Pressing `` correctly goes back in history but doesn't restore the position.

I can't reproduce this on FF74.0+Tridactyl 1.17.1pre3691-2bb4282

Since their tool is all JS we could also grab their implementation of the protocol, have Tridactyl connect to the native messenger through a websocket and have the native messenger...

Apparently we wouldn't even need to go through the native messenger, Firefox accepts websocket connections: https://searchfox.org/mozilla-central/source/devtools/client/framework/target-from-url.js#125

Setting `devtools.debugger.prompt-connection` to false in `about:config` disables this warning. We might be able to do really interesting things with this!

Leaving this here so that I can find it again when the time comes: We might be able to implement js completion using the debugger API (https://developer.mozilla.org/en-US/docs/Tools/Debugger-API) + the parser...

No, there hasn't. You can do live editing by using the browser toolbox though (top-right hamburger menu -> more tools -> browser toolbox).