I know that makes it no longer that way. But in the absence of such problematic parts, it is. In practice, trees usually only really have no more than a few refs, and style/script elements quite frequently don't even exist. So in the common case, it's *almost*.
Also, in reply to your other email, [I did stand corrected on missing the `script` with `textContent` set, but I can just add a case to that particular point][1]. (My experience and knowledge is far better with JS than the DOM.) [1]: https://esdiscuss.org/topic/native-tensor-support#content-8 ----- Isiah Meadows [email protected] Looking for web consulting? Or a new website? Send me an email and we can get started. www.isiahmeadows.com On Sat, Jan 27, 2018 at 10:55 PM, Boris Zbarsky <[email protected]> wrote: > On 1/27/18 9:53 PM, Isiah Meadows wrote: >>> >>> 4. For style elements and ref-accessible elements, you could still >>> execute the changes in set slices, splitting on nodes/callbacks that require >>> awareness of past effects. (This could just be a flag.) However, these are >>> exceedingly rare. > > > This is not longer sounding embarrassingly parallel, fwiw, since you have to > not do later things until earlier things are done under various > conditions... > > -Boris > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
