Bug 827370 has a fix on mozilla-central although in the case of which Gecko is already running, I continue to see about:blank. Currently with my Nightly (02/05) build, when I load a URL via an intent (bit.ly/t.co) from Twitter and Gecko is already running, I continue to see about:blank for a split second.
Is this also a regression from bug 800199?
I've seen this too, and I was investigating yesterday. We're getting an onLocationChange event for about:blank, even though I couldn't find anywhere we explicitly load about:blank when creating a new tab.  was the only candidate I saw, but I confirmed that we do have a valid URI at that point, and we are in fact passing the correct URL in at . I assume something deeper is triggering this.  http://hg.mozilla.org/mozilla-central/file/1eab3e0d7f53/mobile/android/chrome/content/browser.js#l2680  http://hg.mozilla.org/mozilla-central/file/1eab3e0d7f53/mobile/android/chrome/content/browser.js#l689
re comment #0; also reproducible just by launching via a manually added home-screen shortcut
You need to log in before you can comment on or make changes to this bug.