You may be right. It could also be a simple limitation of how the HTML
parser links up to the CSS parser. Still, it would be good to know why
certain tags are redefinable by CSS and some are not, so at least I
could figure out if there's a fix by extending some class or other.
On another note, I wish the HTML parser was inherited from the XML class
so it could be extended. Built into the player as it is means rebuilding
the parser from the ground up just to add functionality, and who's got
time for that?
__________________________________________________________
Joseph Balderson, Flash Developer & RIA Specialist
http://www.joeflash.ca | 416-768-0987
Writing partner, Community MX | http://www.communitymx.com
Développement Bilingue/Francophone disponible
GregoryN wrote:
Hello Joseph,
I think "default tags" are closely connected to TextFormat properties.
So, the content of <b> tag will always have TextFormat.bold = true
and content of <i> tag will always have TextFormat.italic = true
They're just trying to make TextFormat and tags interchangeable where
possible. Remember this terrible <TEXTFORMAT> tag? ;-)
The same is with some other tags you've mentioned: you can't make <li>
to appear w/o bullet or <a> to be not clickable.
Also, I'm curious of the way you're using the <body> tag in flash text
fields...
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
