When the DisplayList mechanism first landed it used SkPaint to compute the bounds of its rendering operations, but that mechanism has drawbacks because we do not track attributes in a way that always produces optimal results from the helper method on that object. Having to stock the attributes in the SkPaint while interpreting the DisplayList also adds some overhead when most of the bounds calculations are simple to compute. Dedicated bounds computations written directly to the DisplayList dispatch interface would be faster and potentially produce more optimal bounds.

(This is an "after-the-fact" issue for PR flutter/engine#28656 to link from the umbrella DisplayList issue for tracking purposes...)