Closed
Bug 762329
Opened 14 years ago
Closed 13 years ago
Add an additional check to test_browserElement_{oop,inproc}_LoadEvents
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: justin.lebar+bug, Assigned: justin.lebar+bug)
References
Details
Attachments
(1 file)
|
1.12 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
We seem to be missing a locationchange event when this test is run in process. The test passes right now, but only because it's lax.
I'll attach a patch which makes the test fail. We should at least figure out why this difference exists.
| Assignee | ||
Comment 1•14 years ago
|
||
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → justin.lebar+bug
| Assignee | ||
Comment 2•13 years ago
|
||
And this now works properly, at least locally. Let's push this patch to try.
| Assignee | ||
Comment 3•13 years ago
|
||
| Assignee | ||
Updated•13 years ago
|
Attachment #630792 -
Attachment description: Patch to make test fail in-process. → Patch, v1
Attachment #630792 -
Flags: review?(21)
| Assignee | ||
Updated•13 years ago
|
Summary: test_browserFrame4 (aka browserElement_LoadEvents) behaves differently in- and out-of-process → Add an additional check to test_browserElement_{oop,inproc}_LoadEvents
Comment 4•13 years ago
|
||
Comment on attachment 630792 [details] [diff] [review]
Patch, v1
Sounds good to me.
Just curious there is 2 waitForAllCallbacks methods in the test file. One check for the 3 booleans while the other check only 2 of them. Was it on purpose?
Attachment #630792 -
Flags: review?(21) → review+
| Assignee | ||
Comment 5•13 years ago
|
||
> Just curious there is 2 waitForAllCallbacks methods in the test file. One check for the 3
> booleans while the other check only 2 of them. Was it on purpose?
That might have made sense before this change to the test, but it doesn't make sense anymore. Thanks for catching that!
| Assignee | ||
Comment 6•13 years ago
|
||
Comment 7•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•