If the DOM is modified on any search results page then the changes do not reflect until the cached version of those results is pulled from memory. This can happen either when the search term is modified and then reverted, or if the search page is exited and entered again, and the search term queried.
The practical effects of this is that it means it is much less streamlined to render search results on the client side.
The potential workarounds are generating the search results server-side (as every single first-party Apple TV app does), or to advise the user to modify their search results.
Potential workarounds tried, but failed, were loading a PopUpMenu and unloading it (no change), loading a DOMView and unloading it (no change), loading another page and then unloading it (no change) and loading and swapping a page and then unloading it (the swap replace the parent page as expected, not simply the searchResults portion).
If the DOM is modified on any search results page then the changes do not reflect until the cached version of those results is pulled from memory. This can happen either when the search term is modified and then reverted, or if the search page is exited and entered again, and the search term queried.
The practical effects of this is that it means it is much less streamlined to render search results on the client side.
The potential workarounds are generating the search results server-side (as every single first-party Apple TV app does), or to advise the user to modify their search results.
Potential workarounds tried, but failed, were loading a PopUpMenu and unloading it (no change), loading a DOMView and unloading it (no change), loading another page and then unloading it (no change) and loading and swapping a page and then unloading it (the swap replace the parent page as expected, not simply the searchResults portion).