diff options
| author | Adam Powell <adamp@google.com> | 2013-09-13 09:22:30 -0700 |
|---|---|---|
| committer | Adam Powell <adamp@google.com> | 2013-09-13 09:26:16 -0700 |
| commit | 758d5a4563a71d4f3f7efbf7e450e8e537abc185 (patch) | |
| tree | 47453a8f967e4f03d25e704551835811e5053688 /core/java/android/os | |
| parent | 26267660957a4428a66d8f142e2bdfa6ce6fe12f (diff) | |
| download | frameworks_base-758d5a4563a71d4f3f7efbf7e450e8e537abc185.zip frameworks_base-758d5a4563a71d4f3f7efbf7e450e8e537abc185.tar.gz frameworks_base-758d5a4563a71d4f3f7efbf7e450e8e537abc185.tar.bz2 | |
Check RelativeLayout's access of its own LayoutParams during measurement
RelativeLayout's use of its own LayoutParams is really old behavior
and something it probably never should have done in the first
place. However at this point it's enshrined compatibility behavior as
fixing this would change the end results of measurement in some cases,
and we've found that apps really love doing strange things with
RelativeLayout that hit all of those edge cases.
The existing behavior ignores this code path if set to MATCH_PARENT or
WRAP_CONTENT, so we'll simply treat missing LayoutParams as the same
case.
Bug 10733375
Change-Id: I8b40b8557d19695ebcd5329aefc1603e2bf4234e
Diffstat (limited to 'core/java/android/os')
0 files changed, 0 insertions, 0 deletions