This is a regression. I don't know why there is an ubuntu-ux task for this exactly. The behavior used to be correct for this flow.
1) From the store scope's preview of an installed scope, tapping "Search" should open the scope with the search URL that is attached to the button (this does actually happen, but for some reason the uninstalled preview is requested on top of the scope as if it's a preview for a result there, tapping the "<" back arrow will actually take you to the newly installed scope from here).
2) Tapping back from the search in the new scope should return to the installed preview page of the click store scope (the place where the search was opened from).
This is a regression. I don't know why there is an ubuntu-ux task for this exactly. The behavior used to be correct for this flow.
1) From the store scope's preview of an installed scope, tapping "Search" should open the scope with the search URL that is attached to the button (this does actually happen, but for some reason the uninstalled preview is requested on top of the scope as if it's a preview for a result there, tapping the "<" back arrow will actually take you to the newly installed scope from here).
2) Tapping back from the search in the new scope should return to the installed preview page of the click store scope (the place where the search was opened from).