VOOZH about

URL: https://bugzilla.mozilla.org/show_bug.cgi?id=646972

⇱ 646972 - An interval started in a background tab ends up clamped to the 1Hz clamp forever


Closed Bug 646972 Opened 15 years ago Closed 15 years ago

An interval started in a background tab ends up clamped to the 1Hz clamp forever

An interval started in a background tab ends up clamped to the 1Hz clamp forever
Core
DOM: Core & HTML
Trunk
x86
Windows 7
defect
Points:
---
RESOLVED FIXED
RESOLVED
FIXED
mozilla5
Iteration:
---
a11y-review
Accessibility Severity
Performance Impact
Size Estimate
Webcompat Priority
Webcompat Score
Tracking Status
relnote-firefox
thunderbird_esr115
thunderbird_esr140
firefox-esr115
firefox-esr140
firefox-esr153
firefox152
firefox153
firefox154
---
QA Whiteboard:
---
Has STR:
---
Change Request:
---
Signature:
None
This bug is publicly visible.

 
Steps to reproduce: 1) Make sure you have new tabs set to open in background. 2) Open the context menu for the "URL" field link on this bug. 3) Select "open in new tab" 4) Wait 10 seconds. 5) Switch to the new tab. Expected results: 10 or so numbers around 1000 followed by a whole slew of numbers around 4. Actual results: all the numbers are about 1000; there is no slew. The problem is that we clamp the timer before storing mInterval in nsTimeout. Patch coming up to fix that. Note that we clam _again_ when using mInterval to reset the timer, so this is exactly what we want: the clamp is only applied when actually setting timers.
Assignee

Updated

15 years ago
Priority: -- → P1
Whiteboard: [need review]
Assignee

Updated

15 years ago
Blocks: 633421
Attachment #523414 - Flags: review?(jst) → review+
OS: Mac OS X → Windows 7
Assignee

Updated

15 years ago
Whiteboard: [need review] → [need landing]
Flags: in-testsuite?
Whiteboard: [need landing] → fixed-in-cedar
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: fixed-in-cedar
Target Milestone: --- → mozilla2.2
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.