791106 - With fresh profile, flashes between displaying "about:home" and "Enter Search or Address" in URL bar on startup

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[William Lachance (:wlach)]

So this is very obvious with the new eideticker startup tests. When you start fennec without a URL, the url bar seems to flash between displaying "about:home" and "Enter Search or Address". From the POV of a user, I think we ought to just display "Enter Search or Address", without the intermediary step.

Example of current behaviour:

http://wrla.ch/eideticker/dashboard/videos/video-1347572002.11.webm

Comment 1

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

I tested Nightly, app was not running and I tapped the homescreen icon, on my Galaxy Nexus. I did not see "about:home" appear. We even have code to ignore any title changes if the title is "about:home":

http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/BrowserToolbar.java#572

The favicon did change from default to firefox. I think the favicon changes because the about:home favicon is specified in the HTML using a <link> tag. Tis means we need to wait for gecko to load, and load that content, before we get the message to change the favicon.

I think Wes had a patch at one time to do the about:home favicon on the Java side.

Comment 2

[William Lachance (:wlach)]

(In reply to Mark Finkle (:mfinkle) from comment #1)
> I tested Nightly, app was not running and I tapped the homescreen icon, on
> my Galaxy Nexus. I did not see "about:home" appear. We even have code to
> ignore any title changes if the title is "about:home":
> 
> http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/
> BrowserToolbar.java#572
> 
> The favicon did change from default to firefox. I think the favicon changes
> because the about:home favicon is specified in the HTML using a <link> tag.
> Tis means we need to wait for gecko to load, and load that content, before
> we get the message to change the favicon.
> 
> I think Wes had a patch at one time to do the about:home favicon on the Java
> side.

Ah, I think this might only be happening because the test is running from a blank profile. So this would likely happen on first run, but not any other time.

Comment 3

[BMO Automation]

Closing all opened bug in a graveyard component