Open Bug 840525 Opened 12 years ago Updated 8 years ago

[SeaMonkey] TEST-UNEXPECTED-FAIL | browser_bug822367.js | Mixed Content Doorhanger didn't appear

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
All
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: mcsmurf, Unassigned)

Details

(Whiteboard: [perma-orange]) 

The new browser_bug822367.js test from Bug 822367 causes a lot of test failures on the Windows SeaMonkey testbox. I'm not sure what exactly needs fixing here, need to look into that. Maybe some UI needs to be ported. Currently quite a lot of tests (probably) fail cause of that:
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/content/base/test/chrome/browser_bug822367.js | Mixed Content Doorhanger didn't appear
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/content/base/test/chrome/browser_bug822367.js | uncaught exception - TypeError: notification is null at chrome://mochitests/content/browser/content/base/test/chrome/browser_bug822367.js:51
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/content/base/test/chrome/browser_bug822367.js | Test timed out
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/content/base/test/chrome/browser_bug822367.js | Found a tab after previous test timed out: https://example.com/tests/content/base/test/file_bug822367_1.html

and after that many other tests fail. I think it might be related to the "Found a tab" problem.
I guess we need to port Bug 822366 then...?
> I guess we need to port Bug 822366 then...?
Yes. And perhaps also Bug 822371 - Implement Mixed Content Blocker Doorhanger - Frontend Changes.
Well, ideally the test of the UI would be near the UI, rather than in a completely unrelated location...
I've written a patch in bug bug 842191 to extend our existing mixed content notification to support the mixed content blocker, however this uses a notificationbox rather than a doorhanger, although it would of course be able to write an override method in the doorhanger binding if someone thought that it would be worthwhile.
(In reply to neil@parkwaycc.co.uk from comment #3)
> Well, ideally the test of the UI would be near the UI, rather than in a
> completely unrelated location...

I filed Bug 842198 on moving the test to browser/.
You need to log in before you can comment on or make changes to this bug.