Tapestry 5
  1. Tapestry 5
  2. TAP5-1631

Tapestry creates client ids for error popups containing the ':' character, which is problematic for some browsers (and some testing tools)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.3, 5.2, 5.1
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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 ?

        Issue Links

          Activity

          Hide
          Howard M. Lewis Ship added a comment -

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

          Show
          Howard M. Lewis Ship added a comment - Discovered a small regression here, that the client-side <div> used for error popups is named "foo:errorpopup".
          Hide
          Hudson added a comment -

          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
          Show
          Hudson added a comment - 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

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Scott mcCarthy
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development