Open
Bug 1302332
Opened 8 years ago
Updated 2 years ago
Consider slowing down timers in x-domain iframes in background tabs
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
NEW
People
(Reporter: smaug, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review |
Adding something like
if (isBackgroundAndXDomain) {
printf("xdomain background %s \n", currentBaseDomain.get());
}
after isBackgroundAndXDomain = !currentBaseDomain.Equals(topBaseDomain);
works as a log. And it is quite depressing. Tons of googlesyndication.com stuff, at least in the pages I tried.
higher value for dom.min_xdomain_background_timeout_value might make sense.
Reporter | ||
Comment 1•8 years ago
|
||
Reporter | ||
Updated•8 years ago
|
Blocks: QuantumDOM
Reporter | ||
Comment 2•8 years ago
|
||
ok, I need to add some max(gMinXDomainBackgroundTimeoutValue, gMinBackgroundTimeoutValue), since on mobile gMinBackgroundTimeoutValue is really long.
Reporter | ||
Comment 3•8 years ago
|
||
Updated•8 years ago
|
Assignee: nobody → bugs
Comment 5•8 years ago
|
||
Note, I believe we have a bug where we don't throttle background timers unless we hit conditions where we would have clamped to 4ms. Andreas is working on it in bug 1316871.
Reporter | ||
Comment 6•8 years ago
|
||
ah. No, I'm not working on this. Leftover from the qDOM work week before we had decided who works on what.
Assignee: bugs → nobody
Flags: needinfo?(bugs)
Comment 7•8 years ago
|
||
Hi Ehsan, my understanding is this issue is part of the qDom tab freezing task and P2 sounds the priority to me. Am I right?
Flags: needinfo?(ehsan)
Comment 8•8 years ago
|
||
(In reply to Hsin-Yi Tsai [:hsinyi] from comment #7)
> Hi Ehsan, my understanding is this issue is part of the qDom tab freezing
> task
No, this was one of the ideas that we were brainstorming on. At this point we're not considering treating iframes specially with regards to background tab freezing.
> and P2 sounds the priority to me. Am I right?
Sure! (To be honest I don't know what these priorities mean. I've so far been ignoring them. :-)
Flags: needinfo?(ehsan)
Updated•8 years ago
|
Priority: -- → P2
Comment 9•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•