flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harbs <harbs.li...@gmail.com>
Subject Re: FlexJS MXML ids and classNames
Date Sun, 07 Aug 2016 21:08:11 GMT

On Aug 7, 2016, at 11:47 PM, Alex Harui <aharui@adobe.com> wrote:

> On 8/7/16, 9:46 AM, "Harbs" <harbs.lists@gmail.com> wrote:
>> OK. That makes sense. (and yes, you understood me correctly)
>> I do think that className should be assigned to the element though via
>> MXML, and there should be an “element id” which should be set-able via
>> MXML.
>> “id” is important if you want some external code to be able to address a
>> piece of your FlexJS app. It’s also important for setting styles via CSS.
> I'm not sure why you are saying that className isn't assigned to the
> element.  The className setter looks like it would.

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.
View raw message