diff options
| author | Bernardo Rufino <brufino@google.com> | 2020-02-04 22:32:34 +0000 |
|---|---|---|
| committer | Bernardo Rufino <brufino@google.com> | 2020-02-06 10:11:34 +0000 |
| commit | 2f167d3823df4c9c6972ee4aa751db2fab3d3b08 (patch) | |
| tree | d52a90cd1dfd76c2861fd909902a8f0b6b30c1a1 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 0a3a6c179cb3169afa851157984d566ba3de2b35 (diff) | |
Don't block app-rendered text toast on apps with targetSdk < 30
We've decided to gate the text toast move on targetSdk due to an app
crash (b/148438364) but decided not to gate the background custom toast
block (in NMS) on targetSdk temporarily to gather dogfood and DP
feedback. This meant that app-rendered text toasts (which are only
possible for apps with targetSdk < 30) were being blocked in NMS since
they were being considered custom toasts.
This brings back the boolean inside Toast class that differentiates
between custom and text toasts for apps with targetSdk < 30, since both
are app-rendered in this case. This code won't be present on final
version and is temporary to gather feedback on dogfood and DP, since
almost no app currently targets SDK 30+. We'll gate both changes (the
system UI move and the bg custom toast block) on targetSdk later on.
Bug: 148761979
Bug: 148794147
Bug: 144754526
Test: Verify that, while on the background:
App with | Custom toast | Text toast
targetSdk < 30 | Blocked | Allowed
targetSdk 30+ | Blocked | Allowed
Test: atest android.widget.cts.ToastTest android.widget.cts29.ToastTest
LegacyToastTest
Change-Id: Id529028bc463034cd2f64a6f2f97e71bc6ea7c36
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions