Closed Bug 472341 Opened 15 years ago Closed 10 years ago

mochitest/chrome fails to get contentViewer on history object

Categories

(Firefox for Android Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jmaher, Unassigned)

References

Details

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.
I'm confused as to why the test is getting to that point at all, since we don't have gBrowser defined AFAIK...
(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.
You guys figured out on IRC that this is because we disable bfcache, right?
(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.
Blocks: 473562
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]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.