- 
                Notifications
    
You must be signed in to change notification settings  - Fork 37
 
Description
Current behaviour
When a user has a certain detailed workflow page opened in the browser and is located on say the Job logs tab, and the user presses "page reload" in the browser, currently the user will be brought back to the first tab of that workflow, i.e. Engine logs tab. This is not good since the original browsing context is lost.
Desired behaviour
The various tabs on the detailed record pages, the Engine logs, the Job logs, the Workspace, etc, should be persistent and page-reload-friendly.
Notes
Beware though when users are using some deeper functionality, such as viewing the logs of the gendata step on the Job logs tab page. When page reload is pressed, could we keep the user staying selected on following the logs of the gendata step?
Ditto for other tabs, such as the Workspace tab, when a user may search for some files matching a pattern, say watching "root" files only from the large workspace; when the user presses page-reload, could we stay on the same tab and same file pattern selection to show ROOT files only? Or will the search pattern be lost when the page is reloaded?
Ideally, the various tab actions of this kind should remain page-reload-friendly so that users could "follow latest logs and files" by simply refreshing the page they are on.
