Closed
Bug 809145
Opened 12 years ago
Closed 12 years ago
Awesomescreen filtering doesn't work if it's initiated from the bookmark or history screens
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect, P2)
Firefox OS Graveyard
Gaia::Browser
Tracking
(blocking-basecamp:+)
People
(Reporter: MattN, Assigned: mbudzynski)
References
Details
(Keywords: b2g-testdriver)
Attachments
(1 file)
Typing in the addressbar/searchbox from the history or bookmarks screen doesn't filter or highlight results like it does from "Top Sites". Having the search box not work like the Top Sites tab makes for a confusing experience which led me to file bug 808917 and bug 808916 for separate filtering support.
Comment 1•12 years ago
|
||
This is by design and is consistent with Firefox Mobile.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Ben Francis [:benfrancis] from comment #1) > This is by design and is consistent with Firefox Mobile. Actually, it does show a filtered awesomescreen on Firefox Mobile and the design[1] simply says: "When the user begins typing, the highlighted text is cleared and the Top Sites/Bookmarks/History tabs disappear. As he types, a list of relevant results filtered by frecency is displayed." [1] https://www.dropbox.com/sh/ygwfxk6chpshxdj/wj9SyPP909/Apps/Browser/R1_AwesomeScreen_v4.pdf (Page 2)
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 3•12 years ago
|
||
Oh sorry, I misunderstood your bug report. I thought this was somehow a meta bug of the other two. Yes, you should get the same awesomescreen results regardless of which tab you start typing from (Top Sites, Bookmarks or History). I think this may be a regression.
blocking-basecamp: --- → ?
OS: Gonk (Firefox OS) → All
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P2
Assignee: nobody → mbudzynski
Comment 4•12 years ago
|
||
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "known P2 bugs found before or during C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
(In reply to Michal Budzynski (:michalbe) from comment #5) > Created attachment 682020 [details] > patch Michal do you meant to ask review to someone?
Attachment #682020 -
Flags: review?(ben)
Comment 7•12 years ago
|
||
Comment on attachment 682020 [details]
patch
Ben told me you need some changes to this code. So carrying r-.
Attachment #682020 -
Flags: review?(ben) → review-
Assignee | ||
Updated•12 years ago
|
Attachment #682020 -
Flags: review- → review?(ben)
Comment 8•12 years ago
|
||
Comment on attachment 682020 [details]
patch
r+me with the completed revisions.
Attachment #682020 -
Flags: review?(ben) → review+
Comment 9•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/243eaf090186e90c296472c80795191d3d688136
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 11•12 years ago
|
||
Thanks everyone. I verified the fix on the stable update channel for b2gtd.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•