[
https://issues.apache.org/jira/browse/TAPESTRY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Caldeweyher updated TAPESTRY-2207:
-----------------------------------------
Summary: async update of <select> with "$1" anywhere inside the <option>
breaks rendering /updating of select list (was: async update of <select> with
"$1" anywhere inside the <option>)
> async update of <select> with "$1" anywhere inside the <option> breaks
> rendering /updating of select list
> ---------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2207
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2207
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.5
> Environment: Internet Explorer
> Reporter: Daniel Caldeweyher
>
> In our app the user can select fee schemes from a drop downlist. Some of
> these fee schemes contain dollar amounts. When this dollar amount starts with
> "$1" an async update of the component will cause the rendering of the options
> to break whereever the options text contains "$1". This only happens during
> async updates, not the original rendering of the drop down list. This happens
> with both @Select and @PropertySelection and only in Internet Explorer. If
> however i call cycle.getResponseBuilder().updateComponent("feeSchemeArea")
> referencing a container around the select instead of
> cycle.getResponseBuilder().updateComponent("feeSchemeSelect"), it renderes
> correctly. I am curtently using the work around of putting a space between $
> and 1. I believe this $1 problem is caused by regex replacements, when dojo
> receives the ajax response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
