Note: we will need something *similar* to this patch, if & when we add an optimization to skip a grid item's "final" reflow if we already reflowed to measure content and that reflow left us at the correct size. That's the point at which we need to consider re-laying-out the contents, even if the size didn't change, due to the fact that the size is now considered definite & will impact percent-resolution on the descendants. That logic will be where we have to take this into consideration in nsFlexContainerFrame. But right now, we don't have that particular optimization in grid.
Bug 1735931 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Note: we will need something *similar* to this patch, if & when we add an optimization to skip a grid item's "final" reflow if we already reflowed to measure content and that reflow left us at the correct size. That's the point at which we would need to consider skipping the hypothetical optimization (and re-laying-out the contents), even if the size didn't change, due to the fact that the size is now considered definite & will impact percent-resolution on the descendants. That logic will be where we have to take this into consideration in nsFlexContainerFrame. But right now, we don't have that particular optimization in grid.
Note: we will need something *similar* to this patch, if & when we add an optimization to skip a grid item's "final" reflow if we already reflowed to measure content and that reflow left us at the correct size. That's the point at which we would need to consider skipping the hypothetical optimization (and re-laying-out the contents), even if the size didn't change, due to the fact that the size is now considered definite & will impact percent-resolution on the descendants. That's where we currently have to take this into consideration, in nsFlexContainerFrame. But right now, we don't have that particular optimization in grid.