On Mon, Jul 16, 2012 at 10:25 PM, Anthony Ferrara wrote:
> This is standard and expected behavior. Since " has no special meaning
> within a document (outside of an attribute declaration), there is no
> requirement to escape it. And the standard practice when parsing XML/HTML
> using a dom based p
Raymond
On Mon, Jul 16, 2012 at 9:30 PM, Raymond Irving wrote:
> Hi Anthony,
>
> Thanks for the feedback. I do get your point about escaping for JavaScript
> but the example shown was just to highlight the entity substitution issue
> which could lead to unexpected results. In this case a develop
