On 11/30/16, 9:51 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>Hi Alex, > >maybe talking about ul/li was bad. UL/LI is working. I think both are >containers, since LI could have direct text or other tags (span, button, >and so on...) >I use it in an example in MDLExample/Tabs >Hope you could revise the rest of the email about output the other kind of >output that is not an html tag node, but a simple text node. Hi Carlos, I'm trying to understand your scenario. Can you post some simple MXML of what you want to do? MXML is not HTML and I'm not sure it should be. Changing MXML might impact IDEs which I don't think we should do. I think text nodes in MXML are expected to be values for properties. In my mind, HTML is oriented toward presenting things to be read, MXML is oriented towards creating things to be interacted with. Thus pieces of text need to be wrapped by some HTMLElement. There is no way to add an id to a TextNode, AFAICT. I could certainly be convinced otherwise... -Alex
