RE: [FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Tigran Najaryan
> From: Alex Harui [mailto:aha...@adobe.com] > > 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 t

RE: [FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Tigran Najaryan
> > 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: > data-flex-id="myid"> > > That sounds like the proper way to do this, if RIATest can run on that > type of attributes. Yes, RIATest can run on any public

Re: [FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Alex Harui
On 4/15/13 7:45 AM, "Erik de Bruin" 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: > data-flex-id="myid"> > > That sounds like the proper way to do this, if RIATest can run on that > type of attr

Re: [FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Erik de Bruin
> 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: 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

Re: [FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Kevin Newman
There are issues with the id of elements in HTML being unique. If they are not unique, they seem to have a negative affect on screen readers. I don't know if that would be a reason to disabled that, but it's something to know. It's for this reason (and the fact that document.getElementById onl

Re: [FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Erik de Bruin
I can't think of no other reason than "it wasn't needed". Unless somehow having an id attribute would mess with JS calls to the object that has the element... But since all JS objects exist in separate namespaces, I don't think it should matter. How about you submit a patch, I create a new public

[FalconJS] populating the 'id' property at runtime

2013-04-15 Thread Tigran Najaryan
I am trying to understand how to make sure the 'id' property is available on the DOM elements. It looks like if I simply modify function org.apache.flex.core.UIBase.prototype.set_id() to directly assign the 'value' to this.element.id it works, the id property becomes available at runtime and is sh