[jira] [Commented] (TAP5-707) Yellow highlight remains on updated zone if zone is re-updated too quickly

["Lenny Primak (JIRA)" <ji...@apache.org>]

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

Lenny Primak commented on TAP5-707:
-----------------------------------

The FlowLogix tapestry library will contain a fix for this bug in the next release. (1.2.3)
which will go out sometime in the next week or so.

Ref: FlowLogix Issue http://code.google.com/p/flowlogix/issues/detail?id=43
This is already available as a snapshot release
                
> Yellow highlight remains on updated zone if zone is re-updated too quickly
> --------------------------------------------------------------------------
>
>                 Key: TAP5-707
>                 URL: https://issues.apache.org/jira/browse/TAP5-707
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2, 5.1.0.5
>            Reporter: Paul Field
>            Assignee: Ulrich Stärk
>             Fix For: 5.2.0, 5.1.0.8
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> By default when a zone updates it shows a yellow highlight that fades away. However, if the zone is updated before the highlight has completely faded then the highlight remains (until the page is completely refreshed).
> To see this in action, go to the JumpStart demo application:
> http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/javascript/ajax
> And *double*-click the link "Refresh time2 only - this is an AJAX-enabled ActionLink".
> (Although JumpStart is currently based on T5.0.18 we see the same behaviour on T5.1.0.5)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira