Looks like min-height/width are the only users of the node at all in ComputedStyleCSSValueMapping::get. I couldn't work out which specs this was coming from but I'd guess we could try and move it to the StyleAdjuster and then remove all the plumbing of Node around these parts?

I think @cbiesinger should know more about this. 

The spec is https://drafts.csswg.org/css-flexbox/#min-size-auto

"On a flex item whose overflow is visible in the main axis, when specified on the flex item’s main-axis min-size property, specifies an automatic minimum size. It otherwise computes to 0 (unless otherwise defined by a future specification)."

So our implementation is actually too simplistic but it does need to know if it's a flex item (or, grid item)

We should use FlatTreeTraversal::parent() here, from where parentStyle comes.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The implementation for the mentioned instance in the report now checks if its layout object is a flex or grid item. No access to parentNode(). Could not see any suspicious use of parentNode() in css/ or style/ now.