Re: Should Attr nodes store their values in a child text node?

On 1/10/08, Kartikaya Gupta <kagupta@rim.com> wrote:
> The value of an Attr
> node can be composed of both text and entity references, for example.
> This means the Attr node would have multiple children. In this case, the
> .value would combine all the children and return a "normalized" value.
> In such a case, .firstChild.nodeValue would not be the same as .value.

Could you show a working example of this where you can either add text
nodes and entityReference nodes to an attribute node or give markup
where this would happen for an attribute during processing?

-- 
Michael