tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott mcCarthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-622) Zone reloading fails in WebKit based browsers (Safari / Chrome) when element IDs contain a colon.
Date Mon, 06 Apr 2009 16:20:12 GMT

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

Scott mcCarthy commented on TAP5-622:
-------------------------------------

Hi Howard,

Changing the colons to underscores (or some other acceptable character) should fix the problem
as well, and remove our dependency on the Prototype update.  (Although I'm sure there are
some other goodies in there worth having, although not relevant to this bug).

In short, as long as I can get my application to work in WebKit browsers, I'm happy!

Cheers

Scott

> Zone reloading fails in WebKit based browsers (Safari / Chrome) when element IDs contain
a colon.
> -------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-622
>                 URL: https://issues.apache.org/jira/browse/TAP5-622
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: Scott mcCarthy
>            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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message