Values vanish from input select boxes when link clicked

This appears to be a bug in the DTD renderer.

I have a page containing some input text boxes and a ice:tree. Clicking on a node in the tree populates the text boxes. Some of the values are quoted (e.g. "word") and these are the ones I have problems with.

If I have a value binding associated with the input box and assign to that a String which is surrounded by literal quotation marks that value is not displayed by the DTD Renderer (which I believe is a bug). If I escape the quotation marks to " then they are displayed as I would expect. However if I then click on a + to expand a section of the tree all of the quoted values vanish and the unquoted values remain.

I haven't yet done enough investigation to determine how generic the problem is but I thought I would bring it to your attention.

Graham.

Thanks Graham,
Yes, I see what you're saying about quoted strings not coming out properly in inputText components. The quotation marks aren't escaped and the output html looks something like:
value=""Node 8"">
which is invalid HTML. I've passed this on to our developers , who'll look into it shortly.

I'm not exactly sure what you mean when you say that when you expand a tree node the all of the quoted values vanish though. Could you elaborate on this?

Thanks,
Philip

I don't believe that expanding a tree node is particularly relevant, it probably happens whenever the screen is rendered.

My point was simply that even if I escape the value in the backing bean to contain " instead of a literal ". The first time the value is displayed it appears on the screen correctly as a " but when the screen is next rendered (e.g by expanding a tree node) the bug manifests and the value gets rendered as value=""node 8"" and the value appears to vanish from the input field.

I would appreciate it if you could find out from your developers if this will be fixed, and the currently projected timeframe in which it will be released.

Thanks

Graham.

Graham,
We've found the source of the bug and are just testing out a fix. So this problem should be solved shortly in the next minor release.

Thanks again,
Philip