Re: [selector-profiles] confusion

On Jul 10, 2013 10:47 AM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:
>
> On 7/10/13 10:16 AM, Brian Kardell wrote:
>>
>> It seems to me that initial/progressive matching is the big problem...
>
>
> The big problem is doing fast updates when the DOM changes.
>
>
>> It's not actually that difficult or even super expensive to match post
>> update, right?
>
>
> What does "post update" mean?
>
> -Boris
>

When DOM changes are complete.  I am suggesting that it should be possible
to simply mark a set of selectors as *something to be named later* which -
at least currently - may not follow the traditional dynamic flow and work
without FOUC, etc. Most of the optimizations that we have now, we only have
because we've had time to optimize them - it is possible that we can figure
out how to move from one category to the other over time, but both should
'work' in some sense:  A large number of pages have at most a few thousand
elements - even a full body scan one the after the DOM is done isn't so
prohibitively expensive as to be worthless - in fact - people do it all the
time and not even natively... and surely we can do better than that
easily... Right?