> The issue may be that there are multiple ways to specify and operate on > innerHTML. If you want to set it directly, then you shouldn't be able to > specify any other children. Hence my earlier suggestion to have a > DivWithInnerHTML component that doesn't subclass Container and only has an > innerHTML property. >
IMHO, this solution does not like me since I think this cases should be eased by us as framework developers and not to give the user 2 components. I think this is a cumbersome limitation in HTML and we should be able to give a solution so MXML/AS3 could make it easy and then output what is expected... -- Carlos Rovira http://about.me/carlosrovira
