<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
So, I've got a few different things we can do, but my preferred solution is to ignore the wrapped text (i.e., don't traverse the children, don't output anything under foo) for the *ajax* case only, and leave it alone for the full response case, since I don't want to break any existing odd-looking code.</blockquote>
<div><br>I think that if a value is provided, then the children should not be rendered. In effect, the value attribute is the content override. So the correct output should be:<br><br><span id="foo">value</span><br>
<br>I don't think Ajax should be a special case, this is a general problem with how the template is interpreted.<br><br>I also feel that we should spec this because it is senseless to have both a value attribute and nested text. Am I missing a case when both would be needed for some other standard output tag?<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>