Open
Bug 451630
Opened 16 years ago
Updated 2 years ago
Chrome mochitests don't actually run as chrome
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: bzbarsky, Unassigned)
References
Details
(Whiteboard: [specialpowers])
Chrome mochitests run in a type="content" docshell. As a result, to actually test chrome behavior (wrappers, various things related to docshell, etc, etc) one has to open a window in the chrome test, then do the whole test in that window. For example, that's what 3 of the 4 docshell/test/chrome directory do... It's a huge hassle, especially since any time the child wants to touch the paren it has to do wrappedJSObject. Ideally, the test harness would actually open the test as the chrome for a window. Less ideally, the behavior would be documented somewhere so people don't have to rediscover it by trial and error.
Updated•16 years ago
|
Component: Testing → Chrome
Product: Core → Testing
QA Contact: testing → chrome
Updated•13 years ago
|
Whiteboard: [specialpowers]
Comment 1•7 years ago
|
||
We could eliminate enablePrivilege without this, after all.
No longer blocks: 462483
Assignee | ||
Updated•6 years ago
|
Component: Mochitest Chrome → Mochitest
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•