custom tabs warmup and mayLaunchUrl not working as expected
Reported by
ismt...@gmail.com,
Jul 1 2016
|
|||||
Issue descriptionExample URL: https://github.com/GoogleChrome/custom-tabs-client Steps to reproduce the problem: 1. install your demo app for custom chrome tabs on android device 2. enter any valid url in the respective field 3. call the press the warmup and mayLaunchUrl buttons which will call the respective functions 4. check your server or inspect with chrome whether you are getting any connection request or pre fetching for some of the content What is the expected behavior? connection to the server and pre-fetching of some of the content should happen on call of mayLaunchUrl method. What went wrong? I tried on the android 6 devices with latest chrome installed but it is not doing anything on call of warmup and mayLaunchUrl. I tested with 10 devices out of which 5 showed this behavior. however after uninstalling and installing the chrome solved the problem i.e. I was able to get the desired result. Did this work before? N/A Chrome version: 50.0.2704.81 Channel: stable OS Version: 6 Flash Version: Shockwave Flash 22.0 r0
,
Jul 5 2016
Hi, and thanks for the feedback! The behaviors of warmup() and mayLaunchUrl() are not guaranteed to be stable over time, and do vary depending on the connectivity, usage history and device type. Typically, warmup() will start and initialize Chrome in the background. At that stage, no network activity is expected. mayLaunchUrl() *may* take actions to speed up the page load, including: - DNS resolution of the host - Opening 2 TCP (or SSL) connections to the host. In these two cases, your server logs may not show anything, since the HTTP GET is not issued. In addition, Chrome may prerender or prefetch the page. This is subject to conditions, to ensure that the user experience is not harmed (excessive battery, memory and bandwidth use). What you're seeing is likely a consequence of throttling, where we temporarily ban an application from prerendering after it issued too many mayLaunchUrl() calls that were not followed by an actual launch of the same URL. Hope that helps.
,
Jul 5 2016
,
Aug 10 2016
,
Aug 19 2016
,
Aug 21 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rsgav...@chromium.org
, Jul 1 2016Owner: ian...@chromium.org
Status: Assigned (was: Unconfirmed)