Closed
Bug 533176
Opened 15 years ago
Closed 15 years ago
Port |Bug 425001 - Tests for bug 400731, 431826 use timers, are fragile| to SeaMonkey
Categories
(SeaMonkey :: Security, defect)
SeaMonkey
Security
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.1a1
People
(Reporter: sgautherie, Assigned: sgautherie)
References
(Blocks 1 open bug)
Details
(Keywords: fixed-seamonkey2.0.3)
Attachments
(2 files)
2.46 KB,
patch
|
neil
:
review+
kairo
:
approval-seamonkey2.0.1-
kairo
:
approval-seamonkey2.0.3+
|
Details | Diff | Splinter Review |
5.11 KB,
patch
|
neil
:
review+
kairo
:
approval-seamonkey2.0.3+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Updated•15 years ago
|
Assignee | ||
Comment 1•15 years ago
|
||
This fixes bug 152526 perma-orange on (my) Windows SM 2.0.x. (At least when running the whole /suite/*. I could make this test fail/regress when running fewer selected tests only: I'll post a workaround I have for that if need be, but I prefer to leave this "unrelated" issue for later...) "approval-seamonkey2.0.1=?": No risk, test only, to help get green waterfall on 2.0.1 (and 2.0.2+).
Attachment #416371 -
Flags: review?(neil)
Attachment #416371 -
Flags: approval-seamonkey2.0.1?
Assignee | ||
Comment 2•15 years ago
|
||
While there, just improve these too. http://mxr.mozilla.org/comm-central/search?string=setTimeout&case=on&find=%2Fsuite%2F.*test
Attachment #416372 -
Flags: review?(neil)
Assignee | ||
Comment 3•15 years ago
|
||
Comment on attachment 416372 [details] [diff] [review] (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests [Checkin: Comment 6+10 & 9+10] "approval-seamonkey2.0.2=?": No risk, test only.
Attachment #416372 -
Flags: approval-seamonkey2.0.2?
Comment 4•15 years ago
|
||
Comment on attachment 416371 [details] [diff] [review] (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js [Checkin: Comment 5 & 8] Doesn't make a lot of difference, but I'd have thought (assuming it works) that newBrowser would have been better than window.
Attachment #416371 -
Flags: review?(neil) → review+
Updated•15 years ago
|
Attachment #416372 -
Flags: review?(neil) → review+
Assignee | ||
Comment 5•15 years ago
|
||
Comment on attachment 416371 [details] [diff] [review] (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js [Checkin: Comment 5 & 8] http://hg.mozilla.org/comm-central/rev/328293ec27b7 (In reply to comment #4) Self-answered in bug 533210 comment 2.
Attachment #416371 -
Attachment description: (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js → (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js
[Checkin: Comment 5]
Assignee | ||
Comment 6•15 years ago
|
||
Comment on attachment 416372 [details] [diff] [review] (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests [Checkin: Comment 6+10 & 9+10] http://hg.mozilla.org/comm-central/rev/d74dc8ab4f13
Attachment #416372 -
Attachment description: (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests. → (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests
[Checkin: Comment 6]
Assignee | ||
Updated•15 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1a1
Comment 7•15 years ago
|
||
Comment on attachment 416371 [details] [diff] [review] (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js [Checkin: Comment 5 & 8] 2.0.1 has been cut, but a=me for 2.0.2
Attachment #416371 -
Flags: approval-seamonkey2.0.2+
Attachment #416371 -
Flags: approval-seamonkey2.0.1?
Attachment #416371 -
Flags: approval-seamonkey2.0.1-
Updated•15 years ago
|
Attachment #416372 -
Flags: approval-seamonkey2.0.2? → approval-seamonkey2.0.2+
Assignee | ||
Comment 8•15 years ago
|
||
Comment on attachment 416371 [details] [diff] [review] (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js [Checkin: Comment 5 & 8] http://hg.mozilla.org/releases/comm-1.9.1/rev/b7f1a3f11318
Attachment #416371 -
Attachment description: (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js
[Checkin: Comment 5] → (Av1) Port m-c browser_bug431826.js changes to c-c browser_bug463504.js
[Checkin: Comment 5 & 8]
Assignee | ||
Comment 9•15 years ago
|
||
Comment on attachment 416372 [details] [diff] [review] (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests [Checkin: Comment 6+10 & 9+10] http://hg.mozilla.org/releases/comm-1.9.1/rev/35e57bd09de4
Attachment #416372 -
Attachment description: (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests
[Checkin: Comment 6] → (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests
[Checkin: Comment 6 & 9]
Assignee | ||
Updated•15 years ago
|
Keywords: fixed-seamonkey2.0.2
Assignee | ||
Comment 10•15 years ago
|
||
Comment on attachment 416372 [details] [diff] [review] (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests [Checkin: Comment 6+10 & 9+10] (Cv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests ... bustage fix, my bad :-< http://hg.mozilla.org/comm-central/rev/e29bae488b4d http://hg.mozilla.org/releases/comm-1.9.1/rev/dbcf7278d19a
Attachment #416372 -
Attachment description: (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests
[Checkin: Comment 6 & 9] → (Bv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests
[Checkin: Comment 6+10 & 9+10]
Assignee | ||
Comment 11•15 years ago
|
||
(In reply to comment #10) > (Cv1) /setTimeout(,0)/executeSoon()/g in /suite/* tests ... bustage fix, my bad > :-< Ftr, there was { TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/suite/browser/test/browser_bug462289.js | mouse on tab selects tab - Got [object XULElement], expected [object XULElement] TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/suite/browser/test/browser_bug462289.js | mouse on tab while focused still activeElement - Got [object XULElement], expected [object XULElement] TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/suite/browser/test/browser_bug462289.js | mouse on another tab while focused still activeElement - Got [object XULElement], expected [object XULElement] }
You need to log in
before you can comment on or make changes to this bug.
Description
•