| commit | 26aa6744970790de086e92014aebf543b4585fb7 | [log] [tgz] |
|---|---|---|
| author | Peter E Conn <peconn@chromium.org> | Fri Mar 22 13:57:53 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Mar 26 14:51:11 2019 |
| tree | f07360ea954989b70d5015859e4dd545f96570ca | |
| parent | da65829d7d4b80c00809c6c4aa7f61f88fc7ca26 [diff] |
✨ Wait for TWA provider to be set in tests. Since the provider was set asynchronously occasionally it wouldn't be set in time for the tests to pick up on it. This change also includes the EnableComponentsTestRule that ensures only the required components are enabled in the manifest for the given tests. Bug: 925762 Change-Id: I68994ab27b55ae7cc516b75e1a088dd1acc03581 Reviewed-on: https://chromium-review.googlesource.com/c/custom-tabs-client/+/1534216 Reviewed-by: Pavel Shmakov <pshmakov@chromium.org> Commit-Queue: 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.