You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/06 00:52:09 UTC

[jira] [Created] (TAP5-1631) Do not create client ids with a ':' character

Do not create client ids with a ':' character
---------------------------------------------

                 Key: TAP5-1631
                 URL: https://issues.apache.org/jira/browse/TAP5-1631
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.0.18
            Reporter: Scott mcCarthy
            Assignee: Howard M. Lewis Ship
            Priority: Critical
             Fix For: 5.1.0.4


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

        

[jira] [Updated] (TAP5-1631) Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1631:
---------------------------------------

    Priority: Major  (was: Critical)
     Summary: Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)  (was: Do not create client ids with a ':' character)

> 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
>
> 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

        

[jira] [Commented] (TAP5-1631) Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097645#comment-13097645 ] 

Hudson commented on TAP5-1631:
------------------------------

Integrated in tapestry-trunk-freestyle #505 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/505/])
    TAP5-1631: Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1165447
Files : 
* /tapestry/tapestry5/trunk/build.gradle
* /tapestry/tapestry5/trunk/tapestry-beanvalidator/src/test/java/org/apache/tapestry5/beanvalidator/integration/TapestryBeanValidationIntegrationTests.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tapestry.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/TapestryCoreTestCase.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/FormTests.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/ZoneTests.java


> 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

        

[jira] [Commented] (TAP5-1631) Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097645#comment-13097645 ] 

Hudson commented on TAP5-1631:
------------------------------

Integrated in tapestry-trunk-freestyle #505 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/505/])
    TAP5-1631: Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1165447
Files : 
* /tapestry/tapestry5/trunk/build.gradle
* /tapestry/tapestry5/trunk/tapestry-beanvalidator/src/test/java/org/apache/tapestry5/beanvalidator/integration/TapestryBeanValidationIntegrationTests.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/resources/org/apache/tapestry5/tapestry.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/TapestryCoreTestCase.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/FormTests.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/ZoneTests.java


> 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

        

[jira] [Closed] (TAP5-1631) Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Updated] (TAP5-1631) Do not create client ids with a ':' character

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1631:
---------------------------------------

    Affects Version/s:     (was: 5.0.18)
                       5.1
                       5.2
                       5.3
        Fix Version/s:     (was: 5.1.0.4)

> Do not create client ids with a ':' character
> ---------------------------------------------
>
>                 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
>            Priority: Critical
>
> 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

        

[jira] [Commented] (TAP5-1631) Do not create client ids with a ':' character

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097614#comment-13097614 ] 

Howard M. Lewis Ship commented on TAP5-1631:
--------------------------------------------

Discovered a small regression here, that the client-side <div> used for error popups is named "foo:errorpopup". 

> Do not create client ids with a ':' character
> ---------------------------------------------
>
>                 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
>            Priority: Critical
>
> 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

        

[jira] [Updated] (TAP5-1631) Do not create client ids with a ':' character

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1631:
---------------------------------------

    Affects Version/s:     (was: 5.0.18)
                       5.1
                       5.2
                       5.3
        Fix Version/s:     (was: 5.1.0.4)

> Do not create client ids with a ':' character
> ---------------------------------------------
>
>                 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
>            Priority: Critical
>
> 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

        

[jira] [Updated] (TAP5-1631) Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1631:
---------------------------------------

    Priority: Major  (was: Critical)
     Summary: Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)  (was: Do not create client ids with a ':' character)

> 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
>
> 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

        

[jira] [Closed] (TAP5-1631) Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Commented] (TAP5-1631) Do not create client ids with a ':' character

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097614#comment-13097614 ] 

Howard M. Lewis Ship commented on TAP5-1631:
--------------------------------------------

Discovered a small regression here, that the client-side <div> used for error popups is named "foo:errorpopup". 

> Do not create client ids with a ':' character
> ---------------------------------------------
>
>                 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
>            Priority: Critical
>
> 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