Closed Bug 1237799 Opened 10 years ago Closed 10 years ago

Fix up some plugin tests to use setTestPluginEnabledState

Categories

(Core Graveyard :: Plug-ins, defect)

defect
Not set
normal

Tracking

(firefox46 fixed)

RESOLVED FIXED
mozilla46
Tracking Status
firefox46 --- fixed

People

(Reporter: mccr8, Assigned: mccr8)

References

Details

Attachments

(2 files)

I found at least a couple of tests (test_bug827160.html and test_object.html) that seem to fail on e10s because they don't use setTestPluginEnabledState. There are probably more. These are easy to find and fix.
Blocks: 1218958
Comment on attachment 8705760 [details] [diff] [review] part 1 - Move test_bug827160.html and test_object.html to plugins directory. When moving these tests to dom/plugins people working on nsObjectLoadingContent or related code in dom/base might miss running these locally. Olli, do you have an opinion here or know who might have?
Attachment #8705760 - Flags: feedback?(bugs)
Yeah, I could just copy a couple of functions into the other DOM directory if people prefer. Though really, the proper solution is to fix SpecialPowers.setTestPluginEnabledState() so it works like the version in plugin-utils...
Comment on attachment 8705760 [details] [diff] [review] part 1 - Move test_bug827160.html and test_object.html to plugins directory. I don't really mind. Given that lots of plugin tests are in dom/plugins, I'd assume anyone doing major changes to nsObjectLoadingContent would need to run tests in dom/plugins anyway.
Attachment #8705760 - Flags: feedback?(bugs) → feedback+
Attachment #8705760 - Flags: review?(gfritzsche) → review+
Attachment #8705761 - Flags: review?(gfritzsche) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla46
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: