Bug 1261842 - Disable browser_contentAreaClick.js for e10s. r?Gijs
The fact that this happened to work in e10s mode is a consequence of
the fact that the initial browser started out non-remote, even in
e10s mode. Coupled with the fact that the browser only loaded
about:blank (which didn't cause a remoteness flip), this essentially
meant we were testing the non-e10s case with a non-remote browser.
MozReview-Commit-ID: DIZVekCYLVh
--- a/browser/base/content/test/general/browser.ini
+++ b/browser/base/content/test/general/browser.ini
@@ -274,16 +274,17 @@ tags = mcb
[browser_bug1015721.js]
skip-if = os == 'win'
[browser_bug1064280_changeUrlInPinnedTab.js]
[browser_accesskeys.js]
[browser_clipboard.js]
subsuite = clipboard
[browser_clipboard_pastefile.js]
[browser_contentAreaClick.js]
+skip-if = e10s # Clicks in content don't go through contentAreaClick with e10s.
[browser_contextmenu.js]
subsuite = clipboard
tags = fullscreen
skip-if = toolkit == "gtk2" || toolkit == "gtk3" # disabled on Linux due to bug 513558
[browser_contextmenu_input.js]
skip-if = toolkit == "gtk2" || toolkit == "gtk3" # disabled on Linux due to bug 513558
[browser_ctrlTab.js]
[browser_datachoices_notification.js]
