Smarter task laying out based off onMeasure
Previously laid out via calls to layoutParams. This isn't as optimized as being baked into the measure + layout system and has the issue of being less flexible. For example, if the device profile changes (e.g. orientation change), we'd have to apply new layout params for all the views. With this CL, we would only need to do this for top-level views and the children will resolve themselves. Bug: 114136250 Test: Check layout on marlin + walleye Change-Id: Iddd503a8844bdde7724d3f804660da61719d5c90 (cherry picked from commit c98f116b)
Loading
Please register or sign in to comment