472341 - mochitest/chrome fails to get contentViewer on history object

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

from the test:
http://mxr.mozilla.org/mozilla-central/source/docshell/test/chrome/bug396519_window.xul#91:
var history = gBrowser.webNavigation.sessionHistory;
if (history.count == gExpected.length) {
  for (var i=0; i<history.count; i++) {
    var shEntry = history.getEntryAtIndex(i,false).
                  QueryInterface(Components.interfaces.nsISHEntry);
    is(!!shEntry.contentViewer, gExpected[i], "content viewer "+i+", test" +gTestCount);
  }
}

we get a valid shEntry, but .contentViewer is always null.  this is causing 26 chrome tests to fail.

If this is not valid in mobile, then we need to modify the test cases appropriately.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

I'm confused as to why the test is getting to that point at all, since we don't have gBrowser defined AFAIK...

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to comment #1)
> I'm confused as to why the test is getting to that point at all, since we don't
> have gBrowser defined AFAIK...

Your answer:
http://mxr.mozilla.org/mozilla-central/source/docshell/test/chrome/bug396519_window.xul#74

We have seen this in other .xul tests too - and they also fail.

Comment 3

[:Gavin Sharp [email: [e-mail]]]

You guys figured out on IRC that this is because we disable bfcache, right?

Comment 4

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to comment #3)
> You guys figured out on IRC that this is because we disable bfcache, right?

Yep. jmaher was going to work around the pref using the automation stuff. fennec will need to figure out what bfcache level we want to use.

Comment 5

[Gordon P. Hemsley [:GPHemsley]]

This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX.

[Mass-change filter: graveyard-wontfix-2014-09-24]