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 branch (ha, look at me thinking all "gitty" ;-)) and you work with that branch? EdB On Mon, Apr 15, 2013 at 11:25 AM, Tigran Najaryan <tig...@gmail.com> 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. > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
