Yep. If you control the output of the attributes and know for a fact that they won't have special characters, then you can use attributes, for instance id's, sequence fields, file paths, etc. but for anything that is user generated where you don't know whether or not there could be special characters (even if you don't think there would be), it's best to go the CDATA route.
And yes, I have learned the hard way, you know where 1 year down the line, all of a sudden the entire application breaks and isn't displaying any data... quite a nightmare. - Taka On Fri, Feb 5, 2010 at 10:33 AM, Jared <[email protected]> wrote: > My rule of thumb is anything that will be used for display text is in CDATA > tags, not attributes > > Sent from my iPhone > > > On Feb 4, 2010, at 8:09 AM, Dave Watts <[email protected]> wrote: > > I always use CDATA tags for text in nodes where special characters might >>> exist. >>> >> >> I really strongly second this. This has been the cause of more >> problems I've seen than I can count. You never know what kind of >> characters you might be getting from a database query. >> >> Dave Watts, CTO, Fig Leaf Software >> http://www.figleaf.com/ >> http://training.figleaf.com/ >> >> Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on >> GSA Schedule, and provides the highest caliber vendor-authorized >> instruction at our training centers, online, or onsite. >> _______________________________________________ >> Flashcoders mailing list >> [email protected] >> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >> > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
