currently we have browser.tabs.remote=true in native fennec, but we do not use this pref. Our reftest harness keys off this and runs all the reftests in remote tabs as a result.
Picking this up...
Assignee: nobody → jet
most of these failures that we depend on pass on later builds of fennec. I have a try server run going with browser.tabs.remote=false and we will see how that goes. I will cleanup these bugs when the time comes.
Created attachment 609813 [details] [diff] [review] remove browser.tabs.remote and cleanup a few manifest files (1.0)
(In reply to Joel Maher (:jmaher) from comment #3) > Created attachment 609813 [details] [diff] [review] > remove browser.tabs.remote and cleanup a few manifest files (1.0) Following up on this one: will this patch (or similar manifest tweakage) do the trick for the remaining failures?
It has been so long, I would honestly have no idea. Reftest and fennec have both changed enough, that we should reevaluate this, basically start from scratch and retest.
odd, this landed Jun 1st (I believe to work around some b2g stuff). So we can actually close this out. I would say we are good to go
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 748088
You need to log in before you can comment on or make changes to this bug.