Empty (blank page) Results page

@Vlad Yup, got a screenshot this time.

I got this again recently but with my desktop. I was investigating it a bit and writing some info here but got distracted by work and forgot about it So I'm working from memory here. Looking back at the reports I guess it might be a different issue since I didn't get a blank page after..

When I got the issue I had some errors in the console. First I checked the response to make sure it looks OK:

I ran a diff on the html from a working page, and it was identical aside from the Nonce and a URL parameter (a token maybe?) being different, so looked good. Same thing with the autosuggestions, they looked identical.

I had some console errors

Interesting, "can't access dead object" is something I never came across before, sounds something like a GC cleaning up a reference to something held in memory...

Found this page on it:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Dead_object

The JavaScript exception "can't access dead object" occurs when Firefox disallows add-ons to keep strong references to DOM objects after their parent document has been destroyed to improve in memory usage and to prevent memory leaks.

This also explains why all examples here are in Firefox..

The interesting thing is that the article specifies that addons cannot hold a strong reference between documents, it initially made me think that the error is caused by some addon interaction. but the error does originate from Kagi's JS

I can't remember the exact line that triggered the error, but I think it was one of these for auto suggestions:

      leadSvgUse.setAttributeNS('http://www.w3.org/1999/xlink', 'xlink:href', svgId),
      leadSvg.appendChild(leadSvgUse),
      leadSvg.appendChild(leadSvgUse),

I ended up remembering to come here because I just encountered the blank-page issue. In this case I'm getting results from kagi.com/stream/ instead, seems like a different method to what I saw when I was debugging last time. No console errors but will look into it a little and see if I can find something

Ok. It seems Kagi loads different JS files based on the context you load the page. If you load kagi.com you'll get
k_lan.min.js. In this context search is submitted by navigating to /search with the search string.

When you load /search (either by the main page, or by browser address bar) you'll load k_sea.min.js. This seems to load results from a websocket by sending events to the page.

If you click the button to switch to a lens, you instead get k_len.min.js.
(I'm interpreting the naming here as kagi_landing, kagi_search, kagi_lense)

Firstly, the browser reports a content-security violation Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). k_len.min.js:1580 (The resulting report request was blocked by ublock, so perhaps you didn't get notified of this before. I disabled ublock and reloaded the page a few times just in case )
After that no console errors occur

But I noticed that k_len.min.js does not have an event listener for the "provider:search" event. (And the html from the socket does not seem to either) It seems to respond to other events, for example 'provider:top_search' will update, even showing me a correction for misspellings.

Here are the event listeners for provider:search

window.addEventListener('provider:search', (() =>{
  const instantTab = document.querySelector('.instant-tab');
  instantTab && (instantTab.hidden = !0)
})),

[
  'provider:search',
  'provider:lenses',
  'provider:news',
  'provider:videos',
  'provider:images'
].forEach((typ=>{
  window.addEventListener(typ, (() =>{
    metric.timeAction('setup_highlight', setupResults)
  }))
})),

And so nothing happens, the content of the page gets cleared.

I can reproduce this 100% consistently, either navigating directly to a search with &l=4 in the uri (any lens will work) or by toggling the button after a normal search. A second search will do nothing, and a third search will clear the results.

Also reproduced on chromium with no extensions