It appears this became a problem when XTile.script started using encodeURI() to encode the request parameters instead of escape(). In the commit history I don't see a specific case tied to the change.. it says only "Refactored XTile to use encodeURI() to encode url parameters".
Jesse - Do you remember why this change was made? The example Dave (my coworker) gives below does indeed break on 4.1.2 but works on 4.0. Thanks, Ben ---------- Forwarded message ---------- From: Dave Kallstrom <[EMAIL PROTECTED]> Date: Jul 31, 2007 4:21 PM Subject: Problem with XTile component To: Tapestry users <[EMAIL PROTECTED]> I am having problem getting the XTile component to correctly send data back to the server. Whenever a user types in a string with an ampersand in it the text after the ampersand as well as the ampersand itself is being cut off. For example "this & that" is being sent back to the server as "this". I believe there was a change made to the XTile component to replace the homegrown regular expression uri encoder to use the javascript encodeURI() function. Could this be the problem? I am certain this was working in previous releases of tapestry. We are currently on 4.1.2 Any help would be appreciated. -- Dave Kallstrom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
