Help: guidance on debugging Vimium on Orion

[southp]

Hello,
I'm currently debugging one particular issue of running Vimium on Orion: after navigating back, the link hints will be broken, and Vimium popup will say "Vimium is not allowed to run on this page".

For the context, Orion is a webkit-based browser made by Kagi. One ambitious goal of it is to support extensions of Chrome and FireFox. I know this particular version of Vimium is never meant to work on a webkit-based browser, but it seems so close so I'd like to take a shot, even if the result is a workaround that can't be merged into trunk.

Here is a screencast of what happened in my test: https://cloudup.com/cPhdHI0M43K (the video is too big, so I uploaded it to CloudUp instead).
By enabling the debug log in the background service worker and vimium_frontend, it looks like there is no longer a content script installed for listening to linkHintsMessage sent from https://github.com/philc/vimium/blob/master/background_scripts/main.js#L536. It's bazzar since some part of the content scripts seem still functioning, like the keystroke listener and the rendering of HUD.

I'm a bit clueless now. I'd be grateful for any guidance 🙇🏼

[southp]

It's potentially better handled at the Orion level, so I've opened a ticket in their tracker here: https://orionfeedback.org/d/11591-extension-the-onmessage-listener-of-a-content-script-is-malfunctioning-after-back-navigation. I'll close the loop here once there is any updates.