On 8/7/16, 2:08 PM, "Harbs" <[email protected]> wrote: > >Never mind. I was wrong about this. > >> Maybe we need an option about whether id gets set on the element. Or >> maybe elements in the main view get their ids set. Andy is right about >> MXML components, but lots of folks only have one instance of each MXML >> component and expect CSS id selectors to work. >> >> Thoughts? > >I would suggest having an additional elementID property and the element >would only have an id assigned if it’s set.
Hmm. I don't think that would be obvious to CSS users. Thinking about this some more, so what if we pass the id on to the element and you create more than one element? Apparently it won't blow up the browser. I'd still lean towards having an option to not set the element id. It might be doable at the document level. Sort of the reverse of what you suggested: if you set "dontSetElementIds" on the MXML top tag, the MXMLDataInterpreter could set some other property like mxmlId instead of id. Thoughts? -Alex
