computeChildPrefAreaHeight and computeChildPrefAreaWidth are incorrect in the case that content bias is set and the "width" is not -1. They ask the child "give me your minimum width based on -1, your pref based on the width, and your max based on -1" (for example). However this is an apples to oranges comparison, because it then takes these three values and does a boundedSize(min, pref, max) on them. However the result of a -1 lookup of minimum width might be "100" for example while a pref width with (100) as the passed width might be 10 for example. But instead of coming out at the right pref height (10), it is bumped up to 100 due to the boundedSize call.