Search API docs on mobile

Stream: general

[Kevin Buzzard]

I just tried to search the API docs on my android mobile; I tried Chrome and duck duck go browsers and I couldn't find elliptic curves by searching in the search box, I just got octopuses.

[Kevin Buzzard]

Dioes it just not work on mobile?

[Eric Wieser]

I think we're running into https://bugs.chromium.org/p/chromium/issues/detail?id=154571

[Yakov Pechersky]

I never got it working on mobile

[Eric Wieser]

https://caniuse.com/?search=SharedWorker suggests it works on mobile firefox

[Riccardo Brasca]

It works on Firefox for me

[Eric Wieser]

It looks like maybe if we used navigator.serviceWorker instead of SharedWorker we'd be ok, but I can't tell whether the semantics are similar enough

[Reid Barton]

An octopus is a hyperelliptic curve right?

[Adam Topaz]

Yes, genus 8

[Adam Topaz]

Works for me on Firefox/android
Screenshot_20211110-172002.png

[Kevin Buzzard]

Also works for me on Firefox! At least that's my own problem solved... . When do we get our own app?

[Eric Wieser]

Eric Wieser said:

It looks like maybe if we used navigator.serviceWorker instead of SharedWorker we'd be ok, but I can't tell whether the semantics are similar enough

It looks like https://github.com/GoogleChrome/samples/tree/gh-pages/service-worker/post-message would be a good template to follow if someone wants to try doing this. But https://stackoverflow.com/questions/29741922/prevent-service-worker-from-automatically-stopping suggests that the background search job might end up being killed due to inactivity; vs the current behavior where clicking a search result can kill the worker if no other tabs are open
.

[Rob Lewis]

I think that any work on this should probably build on doc-gen#131 . There's one remaining issue there, to make the 404 page work with the new search, but honestly we should have fixed and merged that a long time ago

[Eric Wieser]

For me the fact that populating the search index with that PR takes 30s rather than 6s (on my machine) is still a concern

[Patrick Massot]

I forgot this wasn't merged. It's really a shame.

[Rob Lewis]

Eric Wieser said:

For me the fact that populating the search index with that PR takes 30s rather than 6s (on my machine) is still a concern

I wonder what the difference is, I didn't see anywhere close to a 4x slowdown in Chrome.

[Eric Wieser]

Well the indexing data is at least 4x bigger, so it doesn't surprise me that much