-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Update the rendering: consolidate reflows #31871
Copy link
Copy link
Closed
Labels
A-content/scriptRelated to the script threadRelated to the script threadA-layout/2020https://github.com/servo/servo/wiki/Layout-2020https://github.com/servo/servo/wiki/Layout-2020B-feature-trackingThis issue tracks a particular high-level featureThis issue tracks a particular high-level feature
Description
Follow-up to #31242
Step 20 of update-the-rendering says to "update the rendering or user interface of doc and its node navigable to reflect the current state".
I presume that, in Servo, this means issuing a reflow, which is done at https://github.com/servo/servo/pull/31505/files#diff-2c5948584719622eef023c56cdf90e8278971f2f2eda26e7fd0485a24c32be3cR1794
However, there are many calls to reflow made across script. I think it needs a separate PR to track them all down and decide which ones are necessary(but probably not spec conformant), and which ones can be removed, or rather: consolidated into that almost last step that reads "update the rendering or user interface of doc (...)"
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-content/scriptRelated to the script threadRelated to the script threadA-layout/2020https://github.com/servo/servo/wiki/Layout-2020https://github.com/servo/servo/wiki/Layout-2020B-feature-trackingThis issue tracks a particular high-level featureThis issue tracks a particular high-level feature