1389742 - stylo: Remove a few hacky code paths we have from the frame constructor.

Status: NEW

(Core :: CSS Parsing and Computation, enhancement, P4)

Description

[Emilio Cobos Álvarez (:emilio)]

This is a meta bug for the different investigation I'm doing to see if I can kill StyleNewChildren in a reasonable way. Removing StyleNewSubtree may or may not be doable sanely (probably we still needed for NAC / generated content).

I have a few patches and ideas I talked with Boris about, but I didn't want to spam the main stylo bug, so I'll be holding them from this one.

Comment 1

[Bobby Holley (:bholley)]

Really looking forward to seeing this setup improved.

At the same time, we should think carefully about how much we want to bite off for 57 here. If it doesn't block any of our remaining big-ticket items, it may may sense to defer this until 58.

Comment 2

[Bobby Holley (:bholley)]

I think we should probably focus on our blocking issues for now, especially stylist flush performance, memory, and the long tail of random stuff. Only a few weeks left to get to zero.

Comment 3

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals