Closed Bug 602040 Opened 15 years ago Closed 15 years ago

Fix waitForPageLoad for error pages by using the document's readyState

Categories

(Testing Graveyard :: Mozmill, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

(Whiteboard: [mozmill-1.5.1+])

Attachments

(1 file, 1 obsolete file)

We still have problems in correctly detecting the final state of a page load for error pages. The reason is that DOMContentLoaded gets fired once we reach the readyState==complete. Error pages will never reach that state and that's why the named event will never be fired. The state error pages reach is "interactive". The DOM will not be ready by that time, and given that there is no other event fired, we have to wait about 1s. The patch which I will attach in a minute will fix all those problems and correctly detects when a page has been finished loading.
Attachment #481028 - Flags: review? → review?(ctalbert)
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Attached patch Patch v1.1Splinter Review
Missed the important divider for parameters for the baseURI.
Attachment #481028 - Attachment is obsolete: true
Attachment #481037 - Flags: review?(ctalbert)
Attachment #481028 - Flags: review?(ctalbert)
Whiteboard: [mozmill-1.5.1?]
Attachment #481037 - Flags: review?(ctalbert) → review+
Whiteboard: [mozmill-1.5.1?] → [mozmill-1.5.1+]
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [mozmill-1.5.1+] → [mozmill-1.5.1+][mozmill-2.0?]
Whiteboard: [mozmill-1.5.1+][mozmill-2.0?] → [mozmill-1.5.1+][needs-landing-2.0]
Verified fixed with 1.5.1rc1
Status: RESOLVED → VERIFIED
Whiteboard: [mozmill-1.5.1+][needs-landing-2.0] → [mozmill-1.5.1+]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: