Closed Bug 472334 Opened 11 years ago Closed 4 years ago

mochitest/chrome fails to load events in the expected order

Categories

(Core :: Networking: HTTP, defect)

defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

References

Details

in running the mochitest/chrome tests I have a lot of cases where we fail to see events in the appropriate order.  In disucussing with mfinkle yesterday, the problem might be related to lack of disk caching on mobile (although the problem still showed up when I turned on caching).

Basically we get a pagehide with the persisted attribute set to false instead of true.  This causes an unload event to fire which in unexpected.

Right now I am filing this bug as many different tests are failing on it.  For a simple example check out:
_tests/testing/mochitest/chrome/docshell/test/chrome/test_bug112564.xul


The solution might be a fix in fennec, or a fix in the mochitest chrome (maybe to just ignore these tests)
moving to core networkingHttp as this is where tests like 112564 and 92598 are filed under.  Both of those tests fail for what appears to be this same reason.
Component: General → Networking: HTTP
Product: Fennec → Core
QA Contact: general → networking.http
112564 and 92598 are fixed
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.