Closed Bug 711206 Opened 8 years ago Closed 8 years ago
The text "Enter Search or Address" should appear in the awesomebar on the start page AND the awesomescreen from the start page
Web page or screen you were on when you saw the issue: About:home and awesomescreen Steps to reproduce: 1. Start at about:home. The awesomebar shows the string "Nightly Start" 2. Click in the awesomebar 3. The awesomescreen shows the string "about:home" 4. Both these strings do not give the user the idea that tapping in the awesomebar is the way to start a search. What you expected: Have the text "Enter Search or Address" in the field when a user is on the start page AND when they've tapped through to the awesomescreen from the start page. Crash report ID (if applicable):
Assignee: nobody → madhava
Priority: -- → P4
Yes - agreed. Let's do this!
Oh - weird - it's showing the string "Enter Search or Address" for a bit when the page loads, and then it gets replaced with "Nightly Start." Is this because we usually show the URL until we get the title, and we've faked in that string for the URL?
Assignee: madhava → mark.finkle
Whiteboard: [MTD] [user-testing] → [MTD] [user-testing] [polish]
This patch special-cases about:home to keep the urlbar empty, which addresses Mary's concerns from comment 0.
Assignee: mark.finkle → margaret.leibovic
Attachment #589316 - Flags: review?(mark.finkle)
I kinda disagree with #3 in comment 0. All webpages should have a URL. In this case, the text should be selected and ready to be replaced with whatever the user types. #1 is fine and we actually did that in XUL Fennec using the <title> of the about:home page itself - it was set to "Enter Search or Address" I think we should do the same thing here, reducing the amount of hardcoding special behavior for "about:home" - we have enough already.
Comment on attachment 589316 [details] [diff] [review] patch I'll write a new patch to address mfinkle's comments.
(In reply to Mark Finkle (:mfinkle) from comment #4) > #1 is fine and we actually did that in XUL Fennec using the <title> of the > about:home page itself - it was set to "Enter Search or Address" > > I think we should do the same thing here, reducing the amount of hardcoding > special behavior for "about:home" - we have enough already. Actually, this won't prevent the jankiness where we briefly show the "about:home" URL before we get the title of the page (we call setTitle when we first get the url, then we call it again when/if we get a title). Also, it will change from gray placeholder text to black title text. And also, we still keep about:home as a history entry, and if we change the title to "Enter Search or Address" that will show up in the awesomebar results, which seems bad. I agree with your point about all pages having a URL, and I know hard-coding behavior for about:home sucks, but it might be worth it in this place to stop the UI from jumping around. (So just the BrowserToolbar part of the patch.)
Comment on attachment 589316 [details] [diff] [review] patch OK, based on the situation, using the BrowserToolbar.java part of this patch seems like a good compromise. r+ with the AwesomeBar.java part removed.
tracking-fennec: --- → ?
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 12
Comment on attachment 589316 [details] [diff] [review] patch [Approval Request Comment] Mobile-only. Fixes janky UI on startup.
Attachment #589316 - Flags: approval-mozilla-aurora?
Comment on attachment 589316 [details] [diff] [review] patch [Triage Comment] Mobile only - approved for Aurora.
Attachment #589316 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Verified on M-C Samsung Galaxy SII (Android 2.3.4) & Nexus S (Android 4.0.3) 20120119042014
Verified on M-A Galaxy Nexus (Android 4.0.3) 20120126053754 http://hg.mozilla.org/releases/mozilla-aurora/rev/9d5ede8cb11a
You need to log in before you can comment on or make changes to this bug.