Jetpack Search: some interface strings are not being localized

[bluefuton]

Steps to reproduce the issue

1. On your test site with Instant Search enabled, set the site language to 'Français'.
2. Return to the front end of your site and perform a search.

What I expected

If the site language is French, all of the interface language in the Instant Search modal should also be in French.

What happened instead

The modal shows English strings for "Showing popular results", "Sort" and "clear". Interestingly the sort options themselves are correctly translated (e.g. "Pertinence") so some translations are working as expected.

For example: https://lapidoule.com/?s=bebe

Discovered via 4190269-zen.

Screenshots

[bluefuton]

An earlier related issue with some useful information: #15754

My hypothesis is that this is related to the lazy loading changes in #19049, since the translations from jp-search-main.bundle.js appear to be working, but the translations from jp-search.chunk-main-payload-1a2821bfb803906d5e27.js are not.

@sgomes do you know if it's possible to use wp_set_script_translations() in combination with lazy loading?

[sgomes]

@sgomes do you know if it's possible to use wp_set_script_translations() in combination with lazy loading?

I'm afraid I'm not too familiar with this at all, and the documentation doesn't seem to be particularly helpful 😕

At first glance, I suspect the issue could be that the lazily loaded chunk doesn't get the base script's translations, for some reason. If that's the case, perhaps they could be manually exposed on the base and accessed on the lazily loaded chunk, somehow?

[bluefuton]

Thanks @sgomes! Team Global pointed me in the direction of woocommerce/woocommerce-blocks#4392, which looks fairly complicated (more in pxLjZ-6zp-p2#comment-18415).