+1
> On May 22, 2017, at 3:13 PM, Josh Tynjala <joshtynj...@gmail.com> wrote:
>
> Yes, with my proposal, globalID would be translated to HTML. With id, it
> would go back to the classic behavior of adding a member variable to the
> class only and not being translated to a global HTML id.
>
> This change would indeed break existing FlexJS applications that used the
> HTML id in some way (like in CSS). However, we're pre-1.0, so breaking
> changes are still to be expected while we smooth things over. I would
> rather fix id to put it back to the original behavior of affecting the
> current class only than add a workaround like localID/mxmlID for the fact
> that id was overloaded to mean something at the global-level too.
>
> - Josh
>
>
> On Mon, May 22, 2017 at 11:37 AM, piotrz <piotrzarzyck...@gmail.com> wrote:
>
>> Hi Alex,
>>
>> I was going to expand my thoughts on same concerns what Chris mention. If
>> we
>> introduce "localId" which will be responsible for identifying components in
>> MXML we need to also generate "id" - based on those "localId" - cause in
>> many cases "id" will be required in HTML once we set "localId".
>>
>> Some external library may require those "id".
>>
>> Summarize a bit we have so far following ideas:
>> 1) Introduce "localId" or "mxmlId" as entity which is not translated to
>> HTML
>> 2) Introduce "globalId" which will be translated to HTML, but "id" not
>> necessary (Josh Am I understand you right ?) - But that would break
>> existing
>> applications, cause we have right now "id" translation to HTML.
>>
>> Related to introduced new property:
>> 1) Have the compiler check that HTML ids are not used more than once.
>> (Harbs
>> - Globally ?, If id is used more than once in many views ?)
>> 2) Ability set HTML ids (Harbs I need a bit more elaboration on this,
>> cause
>> I do not fully understand)
>> 3) "id" should be generated based on "localId" or make generation based on
>> Chris's suggestions (Piotr, Chris)
>>
>> If I miss something or didn't understand enough please correct me.
>>
>> Thanks for a good discussion on that!
>> Piotr
>>
>>
>>
>>
>> -----
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context: http://apache-flex-
>> development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-
>> classNames-tp54361p61745.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>
