448718 - show autocomplete popup on startup

Status: VERIFIED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Doug Turner (:dougt)]

our current start page is firefox.  fennec needs its own.

we may want to consider local verses remote content.

Comment 1

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

we now have firstrun

Comment 2

[Stuart Parmenter]

we probably want a start page in addition to the first run page

Comment 3

[Madhava Enros [:madhava]]

If there's going to be a start page, could we consider having it be local?  One of my pet peeves with my mobile device is that every time I start it, it starts using up data to get a start page that usually isn't what I want.  I should probably just switch to "nothing" for start page, or something, but I haven't after months and months.

In many ways, I'd be even happier just showing the navigation screen (the one with the awesomebar results and search engines) given that it's local and remarkably similar to what other browsers are offering in the form of a quick dial page.

Comment 4

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

Should we look at the "new tab" work being done in labs?

Comment 5

[Madhava Enros [:madhava]]

An idea for this, with a lot of background: http://madhava.com/egotism/archive/005034.html

Comment 6

[Al Billings [:abillings - ex-MoCo]]

I like the new idea though I do wonder how it would impact performance.

Comment 7

[Madhava Enros [:madhava]]

(accidentally opened another bug for this (bug 511005), when this is the right place for it)

I still like the idea I put forward in comment #5 above, but in the short term I think we should do the following:


When Fennec is launched, other than on First Run (when we show the first run
page), we should bring up the awesomescreen (the navigation screen). 
Eventually, we can make a pref to go to a specific page, but the advantage to
bringing up the awesomescreen is that is entirely local, smart (awesomebar
suggestions) and lets the user tap to go somewhere or search, covering most of
the "start a browser" use cases.

Comment 9

[Madhava Enros [:madhava]]

As Stuart mentions in bug 511005, there are perf concerns with this.  It sounds like there are things we can do to increase the performance of this page getting drawn, which would be good to have anyway.

Comment 10

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

Fixed by bug 523740:
https://hg.mozilla.org/mobile-browser/rev/717d75cb7e0d

Comment 11

[Aakash Desai [:aakashd]]

verified FIXED on builds:

Mozilla/5.0 (Windows; U; Window3sCE 5.2; en-US; rv:1.9.2b4pre) Gecko/20091116 Namoroka/3.6b4pre Fennec/1.0a4pre

and

Mozilla/5.0 (X11; U; Linux armv7l; Nokia N900; en-US; rv:1.9.2b3pre) Gecko/20091116 Firefox/3.6b4pre Fennec/1.0b6pre

and

Mozilla/5.0 (X11; U; Linux armv6l; Nokia N8xx; en-US; rv:1.9.3a1pre) Gecko/20091116 Firefox/3.7a1pre Fennec/1.0b5