The flow representing the body is semantically reconstructed from scratch. Now that doesn't have to actually be what happens at the machine level--I have a TODO that we should reuse parts of flows where possible to accommodate efficient handling of cases like this. This shouldn't affect the safety of the design as long as the "flow-to-be-reused" is appropriately sanitized at the Rust type system level to avoid use-after-free of dead child flows/boxes.
Patrick Boris Zbarsky <bzbar...@mit.edu> wrote: >On 12/14/13 5:18 PM, Patrick Walton wrote: >> Feedback and comments, either here or on the issue tracker, are very >> welcomed! Checking my reasoning and ideas for the TBD areas are >> particularly valuable. > >I'm trying to understand what "The number of primary boxes in each flow > >never changes throughout the flow's lifetime" means in practice. > >Say I have something like this: > > <body> > <span>Text</span> > <!-- repeat that span a bunch of times --> > <span>Text</span> > </body> > >what happens when I remove one of those <span>s from the DOM? What >happens if I add a new <span> to the DOM? What happens if I toggle >"display" on one of those <span>s to "none"? > >-Boris >_______________________________________________ >dev-servo mailing list >dev-servo@lists.mozilla.org >https://lists.mozilla.org/listinfo/dev-servo -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
