725424 - Pressing Menu->Reload repeatedly without waiting for Fennec to finish reloading makes Fennec try to access a wyciwyg URL

Status: RESOLVED FIXED

(Core :: DOM: Navigation, defect, P4)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Snippet of testcase generated during Robofuzz development:

mActions.sendKeys(url);
mAsserter.is(urlbar.getText(), url, "Awesomebar url is fine");
hitEnterAndWait();
// Reload test in fuzzer
mActions.sendSpecialKey(Actions.SpecialKey.MENU);
mSolo.waitForText("Reload");
mSolo.clickOnText("Reload");
// Reload test in fuzzer
mActions.sendSpecialKey(Actions.SpecialKey.MENU);
mSolo.waitForText("Reload");
mSolo.clickOnText("Reload");

Found this using Robofuzz. Not sure if this is a Fennec bug, as I could reproduce w/ manual actions.

Steps:
1. Go to a site, e.g. www.cnn.com on a not-so-fast network (e.g. tethered mobile net)
2. Without waiting for the site to finish loading, press Menu, then Reload. URL should still be correct ( http://www.cnn.com/ ).
3. And press Menu, then Reload again. URL should still be ok.
4. Repeatedly press Menu then Reload without waiting for the site to finish loading. About the 5th time I did it, Fennec switched to accessing:

wyciwyg://0/http://www.cnn.com/

Expected result: Do not access or display the wyciwyg://0/ part. Even if it comes from the cache, I would think.

I am on m-c changeset f69f79d83a30.

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Tested on a Galaxy Tab 10.1.

One may need to repeatedly press Menu -> Reload more than 5 times, I reproduced it again where I had to press the combination 7 times.

Comment 2

[Cristian Nicolae (:xti)]

I was able to reproduce this issue on the latest Nightly build. I went to cnn.com and I tapped on a news title and then I tapped on device Back button.

--
Firefox 14.0a1 (2012-03-22)
Device: Samsung Nexus S
OS: Android 2.3.6

Comment 3

[Cristian Nicolae (:xti)]

I loaded 3 webpages in the same tab and I wanted to go back to the first webpage, so I tapped twice on the back button, without waiting for a fully reload for webpage 2. So after the 2nd back tap, this issue occurred. It would be fine to fix this before the native beta release.

--
Firefox 14.0a1 (2012-03-28)
Device: Samsung Galaxy S
OS: Android 2.2

Comment 4

[:Margaret Leibovic]

This isn't a good mentor bug.

Comment 5

[Andrew McCreight [:mccr8]]

Bug 1489308 is going to get rid of wyciwyg. document.open won't generate a new history entry any more, which is presumably related to what is happening when a load is interrupted.