New issue
Advanced search Search tips

Issue 898005 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 723233
Owner: ----
Closed: Oct 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 723233



Sign in to add a comment

https://www.chromestatus.com/feature/5527160148197376# Not Any Help

Reported by ghbtf...@gmail.com, Oct 23

Issue description

Chrome Version       : 70.0.3538.67 
URLs (if applicable) :http://freecellgui.com/login/about.php
Other browsers tested:
  Not applicable, Chrome only console message

What steps will reproduce the problem?
(1) Not sure what "Background Tab Resource Load Throttling" is.
(2) Only thing possible is use BroadcastChannel and or SharedWorker.
But not getting message 
Active resource loading counts reached to a per-frame limit while the tab is in "background. Network requests will be delayed until a previous loading finishes, or the tab is foregrounded. See https://www.chromestatus.com/feature/5527160148197376 for more details"
on pages that are using these functions.


What is the expected result?
no console message


What happens instead?
getting console message and "Throttling" maybe. Nothing detectable.

Please provide any additional information below. Attach a screenshot if
possible.
Using BroadcastChannel  to send HTML to a page to be displayed.
 SharedWorker is used to ensure no duplicate window.name in domain. So about is checked but not changed. only apppends a sequence number if more than one instance of a page is loaded.

Use to all be done by directly reverencing page and inserting HTML but chrome changed to trow Xdomain errors when not the opener, and did not work on Edge, access denied.

 
Labels: Needs-Triage-M70
Mergedinto: 723233
Status: Duplicate (was: Unconfirmed)
We actively show this message in recent Chrome versions for users to be able to suspect our features breaking their pages.

BroadcastChannel and Workers are not related to this message, but it means a page loaded in background made many requests, and Chrome may handle such excessive resource loading requests slowly.

We will omit this message step by step.

Sign in to add a comment