Tab throttling
Reported by
fenrd...@gmail.com,
Sep 25
|
|||
Issue descriptionChrome Version : 69.0.3497.100 URLs (if applicable) : https://www.chromestatus.com/feature/5527160148197376 Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: OK Firefox: OK Edge: OK What steps will reproduce the problem? (1) Install Chrome (2) Use Chrome (3) Witness throttling message in dev console. What is the expected result? No throttling is expected on background tabs. What happens instead? You throttle background tabs. Why bother having Google Fiber if you're going to throttle? Will happily switch to a cheap local provider to handle your new dial-up socialist methodology. Please provide any additional information below. Attach a screenshot if possible. Seriously Google, what's the problem lately? The new Gmail sucks. The new Chrome sucks. Stop fixing things that aren't broken.
,
Sep 26
Thanks for filing the issue! Tried checking the issue on reported chrome version 69.0.3497.100 using Mac 10.13.1 with the below mentioned steps. 1. Launched Chrome 2. Navigated to a sample webpage 3. Inspected the page -> console Didn't observe any throttling message in devtool's console. Attaching the screenshot for reference. @Reporter: Could you please have a look at the screenshot and let us know if we have missed anything in the process. Any further inputs from your end may be helpful.
,
Sep 26
This happens only when the tab is in background. For some context: this was introduced because the data suggests that this actually improves the metrics (that are expected to reflect user experience) on foreground tabs, which is considered more important. Reporter: thanks for filing this, this is working as intended so closing it, but we will keep collecting the feedback to see if we need further changes in the behavior. Also if this actually breaks anything on particular sites feel free to open a new issue so that we can look into it. Thanks!
,
Sep 26
As developers, this shouldn't need any explaining. Your usage metrics for the general population very well may suggest that this improves "user experience". Who this causes performance loss and wait time for are businesses and software engineers, where daily workflows will immediately open a list of bookmarks in multiple tabs, or perhaps a background task triggers a hot-reload of browser for a framework. Imagine a stock broker whose tools include meta-data, research & analysis, interactive chat, and several watch-lists. The expectation is that the browser has completed pulling necessary resources in background tabs by the time the user puts the tab into the foreground. Again, I will propose that there is no benefit to the user having high-speed internet from a provider like Google Chrome, if that bandwidth is not put to use in a browser's background task. I encourage you to publicly advertise this throttling to your user base. Let them tell you if it's "favorable" for their user-experience, instead of making top-down decisions based on some numbers.
,
Sep 26
Reg: user experience we also have data about how long the tabs that were in background but then switched to foreground reach first-paint/first-meaningful-paint timing, and the data suggests the time doesn't change or even improves a bit. Natural interpretation of this data is that this is not making the majority of users unhappy. But again we are keen to collect more feedback. Thanks for sharing your thought!
,
Sep 26
Okay, thanks for your feedback! Our corporation now considers Chrome to be deprecated. We will use Vivaldi or Firefox for our business needs going forward. Good luck. |
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Sep 25