[ 
https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Howard M. Lewis Ship closed TAP5-1631.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3

> Tapestry creates client ids for error popups containing the ':' character, 
> which is problematic for some browsers (and some testing tools)
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1631
>                 URL: https://issues.apache.org/jira/browse/TAP5-1631
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.2, 5.1
>            Reporter: Scott mcCarthy
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3
>
>
> When attempting to perform a partial page reload such as an AJAX zone, using 
> a WebKit based browser, (such as Chrome or Safari) you will see the following 
> error if the section of the DOM to be updated contains Element IDs with 
> colons in them:
> SYNTAX ERROR - DOM EXCEPTION 12
> Typically, the colons in the IDs are a result of Tapestry dynamically 
> generating an ID for the element, although I'm not suggesting the colon is 
> removed.
> The problem seems to be caused by something in Prototype.  I couldn't tell 
> you exactly what, although this forum messages gives details of a similar 
> problem encountered by another user:
> https://prototype.lighthouseapp.com/projects/8886/tickets/497-prototype-v1603-elementselect-works-wrong-under-safari-and-chrome
> The latest version of Prototype (1.6.1 RC2) fixes the problem.  Although I 
> understand you may not be too keen to use a release candidate version of a 
> library in Tapestry, once Prototype 1.6.1 is released, could this be placed 
> into Tapestry 5.1 ?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to