Well, it makes no sense to me to invent some new property name that sets the "id" of an HTMLElement. I would think we'd get a ton of questions about it. If I"m the only one who thinks that, then I'll stop arguing against it. I thought the consensus upthread was to add localId.
-Alex On 7/16/17, 11:16 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Josh, > >In general if I correct understand that was your idea. I think it is the >simpler solution where we >- Stop set up "id" to HTML id >- Introduce new property which will set up it in html > >+1 for Josh's idea. > >Thanks, >Piotr > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FFlexJS-MXML-ids-and-classNames-tp543 >61p63315.html&data=02%7C01%7C%7C93dc53d5c28f4e49156408d4cc7970af%7Cfa7b1b5 >a7b34438794aed2c178decee1%7C0%7C0%7C636358269329946292&sdata=APogtmBEyf0%2 >BbZVWxl5H%2B%2BT65fTWXDS%2Fys9Ph3aQUmU%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
