Closed Bug 1059521 Opened 11 years ago Closed 11 years ago

testSecurity/testSafeBrowsingWarningPages.js leaves "Report attack" notification open

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Platform:
All
Linux
Type:
defect

Tracking

(firefox32 ?, firefox33 ?, firefox34 affected, firefox-esr24 ?, firefox-esr31 ?)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox32 --- ?
firefox33 --- ?
firefox34 --- affected
firefox-esr24 --- ?
firefox-esr31 --- ?

People

(Reporter: whimboo, Unassigned)

Details

While running some remote tests today against Nightly I have seen that the test testSecurity/testSafeBrowsingWarningPages.js leaves the report attack site notification open. This might cause focus issues with following tests, so we should get this fixed quickly. Can someone take this?
I don't think that this will cause any problems. The next test (testSecurityInfoViaMoreInformation.js) is not affected by the safe browsing notification bar being left open by testSafeBrowsingWarningPages.js. What we could do here is to close the safe browsing notification bar at the end of the test, but this will also require to maximize the window at test start because of Bug 1084289. I'll mark this bug as WFM, please reopen if you think we should implement the approach described above.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.