The call an action that updates the screen returns, bound to the handle it
was called on: the answer is that very handle over the new content, so the
caller continues with the screen it already has, and its back and origin
stay the ones the handle was reached with. Like every member of a handle the
call runs with the services the screen entered with, so its effect
carries no requirements. The answer shows the screen's item lists, so their
items' enter failures are in its error channel (ScreenItemListFailure).
The call an action that updates the screen returns, bound to the handle it was called on: the answer is that very handle over the new content, so the caller continues with the screen it already has, and its
backandoriginstay the ones the handle was reached with. Like every member of a handle the call runs with the services the screen entered with, so its effect carries no requirements. The answer shows the screen's item lists, so their items'enterfailures are in its error channel (ScreenItemListFailure).