[ 
https://issues.apache.org/jira/browse/VCL-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705327#comment-14705327
 ] 

ASF subversion and git services commented on VCL-861:
-----------------------------------------------------

Commit 1696823 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1696823 ]

VCL-861 - Web timetable endless loop

utils.php: modified findAvailableTimes: added conditional to all queries on the 
computer table that makes sure computer is not a VM or that the vmhostid field 
is not null

> Web timetable endless loop
> --------------------------
>
>                 Key: VCL-861
>                 URL: https://issues.apache.org/jira/browse/VCL-861
>             Project: VCL
>          Issue Type: Bug
>          Components: web gui (frontend)
>    Affects Versions: 2.4
>            Reporter: Andy Kurth
>         Attachments: timetable-loop.png
>
>
> The website presents an endless loop when an image is not immediately 
> available for the selected duration.  An animated gif is attached to this 
> Jira issue showing the loop.
> !timetable-loop.png!
> The animation shows an image which is currently available if 2 hours is 
> selected.  When the user changes the duration to 8 hours, the *_Available 
> Times_* box is presented.  The user is shown various available times and 
> selects one.  Upon clicking *_Use Selected Time_*, the *_Available Times_* 
> box reappears and contains the same selections.  The can be repeated 
> indefinitely.
> At the end of the animation, the user selects another timeslot with a shorter 
> duration.  This works as expected.
> Another minor problem is shown in the animation.  After the user changes the 
> duration from 2 to 8 hours, the following happens:
> * *_Loading_* icon appears
> * *_Available Times_* box appears briefly
> *  *_Available Times_* box disappears before user can make a selection
> * *_Loading_* icon reappears
> * *_Available Times_* box appears again and user can make selection
> The hiccup should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to