flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Ent <p...@adobe.com.INVALID>
Subject Re: [FlexJS] getElementIndex()
Date Thu, 22 Jun 2017 15:04:11 GMT
I was wondering why React keeps its own DOM and why it is so fast. Perhaps
this is the reason.

On 6/22/17, 10:56 AM, "Alex Harui" <aharui@adobe.com.INVALID> wrote:

>Feel free to test your theory.  It sounds like duplication of work to me
>as in: The DOM does have some sort of list so why keep our own?  Making
>and manipulation Array is supposedly also not very performant.
>Regarding text nodes, I haven't looked to see when text nodes are
>intentionally children of a UIBase.  Maybe the elements should be allowed
>to be text nodes.
>On 6/22/17, 4:11 AM, "Harbs" <harbs.lists@gmail.com> wrote:
>>Is there a reason we are using the underlying node lists for our
>>collection of elements?
>>I would think that it would be more performant (at the possible cost of
>>some extra memory) to keep a list of FlexJS elements.
>>childNodes are live collections which need to constantly be resolved so
>>they should not be very performant. They also contain text nodes, so I¹m
>>not sure that the index will always be correct.

View raw message