Don't forget to set browser.tabs.remote.separateFileUriProcess in your tests, so you won't get https://treeherder.mozilla.org/logviewer.html#?job_id=100612475&repo=try and https://treeherder.mozilla.org/logviewer.html#?job_id=100612570&repo=try when we merge to beta in three weeks and that pref flips to false. [Tracking Requested - why for this release]: potential merge bustage, potential closed tree, potential delayed b1.

Though I'm just guessing it's only because of that pref, I haven't actually tested that it is.

(In reply to Phil Ringnalda (:philor) from comment #1) > Though I'm just guessing it's only because of that pref, I haven't actually > tested that it is. Thanks philor, pretty much. browser_form_post_from_file_to_http.js is because I forgot to add setting the pref at all. browser_new_web_tab_in_file_process_pref.js is because I'm an idiot and set the prefs after I've opened the first file:// page.

This fixes: browser\base\content\test\tabs\browser_new_web_tab_in_file_process_pref.js dom\html\test\browser_form_post_from_file_to_http.js

Comment on attachment 8869843 [details] [diff] [review] Add and correct pref settings for some file content process tests Review of attachment 8869843 [details] [diff] [review]: ----------------------------------------------------------------- rs=me

marking as blocking 55.

Pushed by bobowencode@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/bcadba7f3b6d Add and correct pref settings for some file content process tests. r=Gijs