Basic usage of the Image search UI results in `Uncaught DOMException: The operation is insecure.` Under Firefox

Havok

Got the same. Images loaded, clicking them made the errors, and then clicking did nothing before going back to the previous page.

Uncaught DOMException: The operation is insecure.
    onclick https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    initImagePreview https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    renderImagesPage https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    <anonymous> https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    onSocketMessage https://kagi.com/images?q=testing:356
    onSocketMessage https://kagi.com/images?q=testing:356
    connect https://kagi.com/images?q=testing:356
    onsubmit https://kagi.com/images?q=testing:356
    EventHandlerNonNull* https://kagi.com/images?q=testing:356
    EventListener.handleEvent* https://kagi.com/images?q=testing:356
k_ima.min.js:1
    onclick https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    (Async: EventHandlerNonNull)
    initImagePreview https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    renderImagesPage https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    <anonymous> https://kagi.com/asset/v1/js/k_ima.min.js?v=c8dda5c831e57e322ba05aa121fa11d497dd2a9d:1
    onSocketMessage https://kagi.com/images?q=testing:356
    forEach self-hosted:157
    onSocketMessage https://kagi.com/images?q=testing:356
    (Async: EventHandlerNonNull)
    connect https://kagi.com/images?q=testing:356
    onsubmit https://kagi.com/images?q=testing:356
    (Async: EventHandlerNonNull)
    <anonymous> https://kagi.com/images?q=testing:356
    (Async: EventListener.handleEvent)
    <anonymous> https://kagi.com/images?q=testing:356

Elifino

Same issue here with Firefox, very annoying, upvoted as I feel this is a major usability issue.

pixel

Hey all, just merging this in with the other post regarding this.

nat posted something that could potentially help, but we should not be navigating this much in the first place.
The history calls exceeded errors feel very weird but it's also something I cannot reproduce even when spamming images/queries.

It seems to be firefox specific, across multiple operating systems - all seemingly on 134.0 and up.

We are still looking into the issue and will keep you updated - thanks.

LoganKaser

Changing dom.navigation.navigationRateLimit.count from the default of 200
to 0 (limit disabled) does “fix” this for me, I suggest you check your about:config, it's possible this
default is not being migrated to older installs, or something like that.
This does suggest that something Kagi is doing is calling the history / location API a lot more than it should

LoganKaser

https://github.com/ClearURLs/Addon/issues/412
https://github.com/ClearURLs/Addon/issues/409
I think this may be related to these issues.
In particular, this “feature”:

Seems to be necessary to trigger the issue (it's on by default). Following those issue threads, it looks like that change may be reverted soon, which would unbreak kagi.
At the very least, I'm now pretty sure that the issue was extension related, at least for me.
FWIW it's a popular extension, probably that alone is enough to explain the incident rate.

bcampbell

LoganKaser

I can confirm that I use the ClearURLs extension and that disabling that 'Prevent tracking injection over history API' feature does indeed resolve the issue, thanks so much for that great detective work! Looks like an upstream bug with that extension as it's breaking a number of websites, including Google, Bing, DuckDuckGo and GitHub as well as Kagi. Probably would be acceptable to let Kagi users know that they should turn that feature off until a bug fix is available from the extension vendor.

pixel

Interesting!
I can reproduce the issue with the extension.

@Elifino / @Havok / @bcampbell
Are you using this extension?
If so, please try without.

lbatalha

I can confirm that disabling the History API Injection protection option in that extension fixes this, it does seem to be a bug with the extension that effects various websites

pixel

Closing this - since it appears to be related to the ClearURLs extension.
If anyone has this issue without the extension, please feel free to comment and we can re-open.

« Previous Page