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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3, 5.2, 5.1
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Scott mcCarthy
• Created: 05/Sep/11 22:50
• Updated: 06/Sep/11 00:07
• Resolved: 05/Sep/11 23:24

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

• is a clone of: TAP5-622 Client ids should not contain the ':' character, as that can confuse WebKit-based browsers