On 4/15/13 7:45 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> As an alternative to using the browser's native id attribute (in cases where
>> that might be a problem) you can use a data attribute: <input
>> data-flex-id="myid">
>
> That sounds like the proper way to do this, if RIATest can run on that
> type of attributes.
>
> I didn't check, but doesn't the compiler on the Flash side mind if you
> try to use the same id twice?
Yes, but only with in an MXML file. I think Kevin is pointing out a
potential issue where you have several MXML files of which more than one
uses the same ID.
That's the main reason I didn't wire set_id to the DOM's id: I wasn't sure
of the implications. I also was trying to find time to re-read the Web
Components/Shadow DOM proposals to understand how id's work there.
But realistically, anyone with multiple MXML files trying to make an
accessible HTML will probably have to come up with their own scheme to make
sure id's are unique within their app.
And since we still need a way for folks to set the id in order to get
accessibility to work, it might be best for now to just gamble and wire up
set_id to the id. No need for a branch. Just do it. I'll try to get
someone to think about the accessibility issues.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
