Since you have some experience working with this API, I'm wondering if you have some ideas on how I can accomplish
All things being equal, I'd want to just start typing in gnome and have the search-provider report results provided directly by chrome, but I've found that chrome's not happy about sharing data. Periodically exporting, encoding, and searching a static file might be an easier way to get this implemented at least for proof of concept.
I've been grafting onto the Epiphany code base for now to interface with gnome-shell via tie ephy-search-provider structure to see how it performs.
I started working on this problem: https://discourse.gnome.org/t/modifying-epiphany-search-provider-to-work-with-google-chrome-creating-a-google-chrome-search-provider-for-gnome and as I proceeded, I started to focus on what would be most relevant to me as results in gnome-search. I realized that, for much the same reason as you, the omnibox is a great place to get suggestions since this is how I use chrome already (no bookmarks/shortcuts, just omnibox, a lot of tabs, and some PWAs).
Since you have some experience working with this API, I'm wondering if you have some ideas on how I can accomplish All things being equal, I'd want to just start typing in gnome and have the search-provider report results provided directly by chrome, but I've found that chrome's not happy about sharing data. Periodically exporting, encoding, and searching a static file might be an easier way to get this implemented at least for proof of concept.
I've been grafting onto the Epiphany code base for now to interface with gnome-shell via tie ephy-search-provider structure to see how it performs.