Closed
Bug 183604
Opened 22 years ago
Closed 22 years ago
The DOM code should re-use the "OS" timer for inteval timers
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla1.3beta
People
(Reporter: jst, Assigned: jst)
Details
(Whiteboard: [HAVE FIX])
Attachments
(3 files, 1 obsolete file)
9.45 KB,
patch
|
Details | Diff | Splinter Review | |
8.86 KB,
patch
|
caillon
:
review+
peterv
:
superreview+
|
Details | Diff | Splinter Review |
9.32 KB,
patch
|
Details | Diff | Splinter Review |
Now that the timer code supports re-initializeing existing timers we should take
advantage of that in the DOM timeout code. Patch coming up.
Assignee | ||
Comment 1•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Attachment #108274 -
Flags: superreview?(bzbarsky)
Attachment #108274 -
Flags: review?(caillon)
Comment 2•22 years ago
|
||
Comment on attachment 108274 [details] [diff] [review]
Don't re-create timers for inteval timeouts, re-use the existing one.
Man, a diff -w of some sorts would have really been nice here.
>+ // Reschedule timeout. Ignore any errors since nobody who
>+ // listens them will care anyways.
listens _to_ them
r=caillon
Attachment #108274 -
Flags: review?(caillon) → review+
Comment 3•22 years ago
|
||
Comment on attachment 108274 [details] [diff] [review]
Don't re-create timers for inteval timeouts, re-use the existing one.
sr=bzbarsky with that comment change.
Attachment #108274 -
Flags: superreview?(bzbarsky) → superreview+
Assignee | ||
Comment 4•22 years ago
|
||
Comment changed, I looked at a diff -w of this before attaching the diff, but it
didn't actually help much so I ended up not attaching it. Thanks for the reviews.
Status: NEW → ASSIGNED
Priority: -- → P3
Whiteboard: [HAVE FIX]
Target Milestone: --- → mozilla1.3beta
Assignee | ||
Comment 5•22 years ago
|
||
Comment on attachment 108274 [details] [diff] [review]
Don't re-create timers for inteval timeouts, re-use the existing one.
Bah. That didn't work, I don't know what I was thinking...
New patch coming up...
Attachment #108274 -
Attachment is obsolete: true
Assignee | ||
Comment 6•22 years ago
|
||
This fixes this bug, for real this time. This also eliminates a bunch of silly
assumptions about who owns what based on the existance of a OS timer or not.
This should be far more maintainable from here on. diff -w coming up of this
one.
Assignee | ||
Comment 7•22 years ago
|
||
Assignee | ||
Updated•22 years ago
|
Attachment #108963 -
Flags: superreview?(bzbarsky)
Attachment #108963 -
Flags: review?(caillon)
Comment 8•22 years ago
|
||
Comment on attachment 108963 [details] [diff] [review]
diff -w
I thought I marked this already with r=caillon. Anyway, I think that bz is on
vacation now, so unless you wanna wait like a month or so, maybe peterv should
sr this.
Attachment #108963 -
Flags: review?(caillon) → review+
Assignee | ||
Updated•22 years ago
|
Attachment #108963 -
Flags: superreview?(bzbarsky) → superreview?(peterv)
Comment 9•22 years ago
|
||
Comment on attachment 108963 [details] [diff] [review]
diff -w
sr=peterv with the minor change you wanted to do for isInterval.
Attachment #108963 -
Flags: superreview?(peterv) → superreview+
Assignee | ||
Comment 10•22 years ago
|
||
Assignee | ||
Comment 11•22 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•