diff options
| author | Jeff Sharkey <jsharkey@android.com> | 2015-09-29 13:04:46 -0700 |
|---|---|---|
| committer | Jeff Sharkey <jsharkey@android.com> | 2015-09-29 13:04:48 -0700 |
| commit | cc2ae6b421353e03160df3b05ce9042b8a5ff8cc (patch) | |
| tree | 539c8bf55d7e7d4335d0db5b4f9ffd673b37a384 /cmds/appops/src/com | |
| parent | c25d546050423845c42a5e8cc8e356caa1f4f71a (diff) | |
| download | frameworks_base-cc2ae6b421353e03160df3b05ce9042b8a5ff8cc.zip frameworks_base-cc2ae6b421353e03160df3b05ce9042b8a5ff8cc.tar.gz frameworks_base-cc2ae6b421353e03160df3b05ce9042b8a5ff8cc.tar.bz2 | |
Relax auto-launch checks for GET_CONTENT.
When a developer wraps an intent with Intent.createChooser(), they're
indicating that the user should always be prompted, instead of using
any "always use" defaults. A recent CL changed the chooser behavior
to ensure that UI is always shown in the case where there is only one
match.
However, this caused us to start prompting for the GET_CONTENT intent,
for which there is only ever one DocumentsUI system app. Since that
app delivers on the createChooser() contract described above, we're
okay automatically launching it.
Bug: 24464358
Change-Id: I0279d3343479c134a35f41ddf3cb4204d0ae6a90
Diffstat (limited to 'cmds/appops/src/com')
0 files changed, 0 insertions, 0 deletions