Bug 646416 - Job page - Ajax jerky
Summary: Job page - Ajax jerky
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: 23.0
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard: UX
Depends On: 1263917
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-25 10:59 UTC by Raymond Mancy
Modified: 2016-07-07 23:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-07 23:11:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Raymond Mancy 2010-10-25 10:59:55 UTC
Updating the DOM on the job page is done in jerky movements and kind
of makes me motion sick.
Would be good to change this.

Comment 1 Dan Callaghan 2012-10-04 05:38:15 UTC
Is there any way we can fix this, short of redesigning the entire job page? Can you take some dramamine instead? :-)

Comment 5 Dan Callaghan 2015-09-17 05:45:24 UTC
(In reply to Dan Callaghan from comment #1)
> Is there any way we can fix this, short of redesigning the entire job page?

Turns out re-designing the job page is what we are doing.

Comment 8 Dan Callaghan 2016-04-07 22:43:45 UTC
Yes Raymond's original description was not very clear. He was talking about the case where you have the job page open (for a job containing multiple recipes) and you have expanded all recipes' results. Then when you refresh the page, it shows the job page and then loads each recipe's results in sequence causing the page to jerk around as it expands (hence "jerky").

Anyway yes we can mark this as VERIFIED based on the fact that the new job page doesn't show any recipe results at all, and the recipe page renders results onload, there are no asynchronous requests. So this problem doesn't exist anymore.

Comment 9 Dan Callaghan 2016-07-07 23:11:26 UTC
Beaker 23.0 has been released.


Note You need to log in before you can comment on or make changes to this bug.