The default bug view has changed. See this FAQ.

Javascript/SVG Animation not working correctly in background tabs

VERIFIED FIXED in Firefox 7

Status

()

Core
SVG
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: Michael, Unassigned)

Tracking

5 Branch
mozilla7
x86
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox5- affected, firefox6+ wontfix, firefox7 fixed)

Details

(Whiteboard: [fixed in 7 by 647001 but not in 6], URL)

(Reporter)

Description

6 years ago
User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0

The dots on the chart will get stuck on the right hand side of the graph until the next data update.

Reproducible: Always

Steps to Reproduce:
1. Open http://www.highcharts.com/demo/dynamic-update
2. Allow the graph to load and tick a few times
3. Switch to another tab for ~15 seconds
4. Come back to the tab and note the position of the dots and line before the next update tick.

Actual Results:  
Dots all clumped on the right side of the graph.

Expected Results:  
Dots continuing to move with the line as they do when the tab is in the Foreground

Hardware acceleration is on.
(Reporter)

Updated

6 years ago
Version: unspecified → 5 Branch
(Reporter)

Updated

6 years ago
Summary: Javascript/SVG Animation not working 100% in background tabs → Javascript/SVG Animation not working correctly in background tabs
(Reporter)

Comment 1

6 years ago
Works as expected in Firefox 4.

Comment 2

6 years ago
Maybe this is caused by Bug 633421.
See
https://developer.mozilla.org/en/DOM/window.setTimeout#Inactive_tabs
and
https://developer.mozilla.org/en/firefox_5_for_developers#DOM

Comment 3

6 years ago
or bug 586201 Does setting layout.throttled_frame_rate to 60 in about:config have any effect?
Component: General → SVG
Product: Firefox → Core
QA Contact: general → general
At first glance, looks like a likely duplicate of bug 647001... but I don't see why, given that the page seems to only use 1000ms timeouts.  Or is there a faster-running timeout on there somewhere?
Depends on: 647001
jst, if we think this is something we need to fix for Fx5, I can try to write a quick patch for bug 647001 and see whether it helps...

Robert, that pref no longer does much of anything.
Status: UNCONFIRMED → NEW
status-firefox5: --- → affected
tracking-firefox5: --- → ?
Ever confirmed: true
Might also be related to bug 658189...
Unlikely; if I switch background tab setTimeout to a lower value (even 200ms is enough) the problem goes away.
Too late for 5, but since this will represent a regression in 5 so +'ng for tracking-6
tracking-firefox5: ? → -
tracking-firefox6: --- → +
Blocks: 633421

Comment 9

6 years ago
Fixed by bug 647001?
(Reporter)

Comment 10

6 years ago
The behavior is fixed in 7, I was still able to get it to occur once or twice in the 10 minutes that I tried. Nothing reproducible however.

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Updated

6 years ago
status-firefox6: --- → affected

Comment 11

6 years ago
Are we going to try to do anything for 6 or are we calling this bug "done"?
status-firefox7: --- → fixed
Whiteboard: [fixed in 7 by 647001 but not in 6]
I think we're calling this done....  The only fix here is to fix bug 647001, and that one wasn't approved for 6.
Target Milestone: --- → mozilla7
status-firefox6: affected → wontfix
Mozilla/5.0 (Windows NT 6.1; rv:7.0a2) Gecko/20110810 Firefox/7.0a2
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a2) Gecko/20110810 Firefox/7.0a2
Mozilla/5.0 (Windows NT 6.1; rv:8.0a1) Gecko/20110810 Firefox/8.0a1
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:8.0a1) Gecko/20110808 Firefox/8.0a1

I have tested it on these builds of Aurora and Nightly, and the bug does not reproduce anymore.
Can I change the status to VERIFIED FIXED?
Thanks!

Comment 14

6 years ago
Setting resolution to verified Fixed on Mozilla/5.0 (Windows NT 6.1; rv:7.0) Gecko/20100101 Firefox/7.0

The dots are moving correctly.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.