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 only
returns one element, not a collection even if there are more than one
elements with the same id) that ASP.NET messes with all of your ids in a
control (which ends up being extremely annoying down stream).
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">
Kevin N.
On 4/15/13 5:25 AM, Tigran Najaryan wrote:
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 shown by Firebug.
Is there a reason why set_id() currently does not do it? If this
modification is acceptable I will submit a patch.
Tigran.
