Currently, when you're searching for something under the about:start window, there's no progress bar while the website is loading giving no feedback to the end user. Because we take a few seconds to complete this search, it's very unintuitive in my opinion. There's been a few times were I thought my "enter" didn't register with the browser, or the window has stalled some how. I think we should either: a) speed up the URL text field search b) add some type of indication that fxmetro is doing something when a user is searching via the URL text field (I personally like (a) better but I'm not sure if that's feasible) Looks like work from Bug #934714 removed progress bar under the about:start window. Video of the issue: - http://youtu.be/wAyh9PstL7I Steps to reproduce the issue: 1) Open fxmetro 2) Under the about:start screen, type something into the search field and hit "Enter" 3) You'll notice that there's no progress bar being displayed when loading the search is in progress Current Behavior: - Searching through the URL text field under the navigation app bar is taking longer than expected Expected Behavior: - Once I hit "Enter", fxmetro should give the user some feedback that the search is in progress. Should probably take a lot quicker than it currently is. Found the issue using the following build: - http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-02-27-03-02-03-mozilla-central/ - http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-02-27-00-40-02-mozilla-aurora/
This was made worse by bug 969356. We can't use [startpage] attribute for hiding progress bar anymore. When then search engine response is slow it really seems like nothing is happening.
Status: NEW → ASSIGNED
Assignee: nobody → rsilveira
QA Contact: kamiljoz
Whiteboard: p=2 → p=2 s=it-30c-29a-28b.3 r=ff30
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.