| commit | 48b80b05b7d1e8df09be39f5a31f82c429886a7b | [log] [tgz] |
|---|---|---|
| author | Pavel Shmakov <pshmakov@google.com> | Tue Feb 05 16:31:54 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Feb 05 16:34:55 2019 |
| tree | dd1e38f9375ea5c405e550212d7d4a568bbdb8b6 | |
| parent | b37717cf6e39bc192225c9e6589e01ca722e0c08 [diff] |
Call warmup for Chrome 72 when launching TWAs Chrome 72 needs the client.warmup() call, whereas in Chrome 73 this requirement was removed to make TWA startup faster. LauncherActivity should account for both cases. Bug: 928686 Change-Id: I1c277c5df4028001230a3e35133e7df4921dcb9c Reviewed-on: https://chromium-review.googlesource.com/c/1454656 Commit-Queue: Pavel Shmakov <pshmakov@chromium.org> Reviewed-by: Peter Conn <peconn@chromium.org>
Chrome Custom Tabs provides a way for an application to customize and interact with a Chrome Activity on Android. This makes the web content feel like being a part of the application, while retaining the full functionality and performance of a complete web browser.
Using Custom Tabs should be easy. This repository hosts examples and in-depth documentation. The examples are importable as projects into the Android Studio.
We want to hear your feedback! Please create bugs and start discussions using this template. Please use the template for any issues related to the Custom Tabs APIs, their implementation in Chrome, the examples in this repository, and related functionality of the Android Support Library.
Note: we know that the GitHub issue tracker is great! However, since Custom Tabs is mostly driven by Chrome developers, and we want to keep all bugs in one place, we prefer the Chromium issue tracker at the moment.
We accept contributions to Custom Tabs examples and documentation. Please see our contributor's guide.