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.

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:

<span id="foo">value</span>

I don't think Ajax should be a special case, this is a general problem with how the template is interpreted.

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?

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.