Bug #2338

Pipeline instance reloads interfere with user's tab selection

Added by Brett Smith over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Start date:
03/12/2014
Due date:
% Done:

100%

Estimated time:
(Total: 2.50 h)
Story points:
1.0

Description

Issue:
If I view the pipeline instance of a running pipeline, the page reloads every so often to show me the latest status. However, this reload consistently puts me back to viewing the "Components" tab of the page, even if I had switched to another tab. This takes me away from my work.

Steps to reproduce:
  1. Start running a pipeline.
  2. On the Workbench, go to Activity → Recent pipeline instances → Select a running pipeline
  3. On the pipeline page, switch to another information tab, like Graph or JSON.

Expected results:
I can take all the time I like to review the information on the selected tab, without interruption.

Actual results:
When the page reloads, the Components tab is selected and put in front of me.


Subtasks

Task #2520: Stash and restore current tab selection when replacing body content in js viewResolvedTom Clegg

Task #2563: Review 2338-maintain-active-tabResolvedTom Clegg

History

#1 Updated by Brett Smith over 6 years ago

  • Project changed from Arvados to Arvados Private
  • Release set to 6

#2 Updated by Tom Clegg over 6 years ago

  • Release deleted (6)

#3 Updated by Tom Clegg over 6 years ago

  • Target version set to 2014-04-16 Dev tools and data/resource management

#4 Updated by Tom Clegg over 6 years ago

  • Story points set to 1.0

#5 Updated by Tom Clegg over 6 years ago

  • Assigned To set to Tom Clegg

#6 Updated by Brett Smith over 6 years ago

jQuery is not my forte, but it makes sense and is sensible.

I think it'd be possible to test this in an integration test. You could go to a running pipeline page, select a tab, make a small API request just to change updated_at, wait N seconds, and make sure that your tab is still selected. Admittedly this would probably be twice as much code as the bugfix, but I bet the hard parts would come in handy for future test development.

But if you think this is a case where we should defer testing for lack of infrastructure, I think this is good to merge. Thanks.

#7 Updated by Anonymous over 6 years ago

  • Status changed from New to Resolved

Applied in changeset arvados|commit:506e5678188ff5a51d4e38558fe8fc0fb4357be2.

Also available in: Atom PDF