Closed Bug 739551 Opened 13 years ago Closed 13 years ago

AwesomeScreen Doesn't Match Multiple Fields

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 738961

People

(Reporter: tech4pwd, Unassigned)

Details

(Whiteboard: parity-desktop)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120326 Firefox/14.0a1 Build ID: 20120326031149 Steps to reproduce: I'm not sure how to file this bug. Basically, it was mentioned in another bug I filed that most users attempt to use sync via AwesomeBar rather than about:sync-tabs. That was a strange concept to me completely as if I knew the page title, I'd just pull up the page rather than hope for a list of tabs to trigger something. Anyway, I thought I'd give it a go and started taking more notice of the tab titles and see what it was like. There are fundamental problems with this approach to sync tabs and the main one being that Fennec can't match tabs via the AwesomeScreen properly. Actual results: Have a shed-load of tabs open on desktop, attempt to find said tabs on Fennec via text. Type in a part of the page title and part of the domain and you're given zero results. Expected results: Your search results should be further refined and you should be given a visual indication as to open tabs on a separate device. Basically the issue here is that should you attempt to search 'page title' and 'URL/domain', you're search results return empty. This behaviour is intrinsically broken given what users are accustomed to on desktop.
OS: Windows 7 → Android
Hardware: x86 → ARM
Summary: Awesome Bar Doesn't Match Properly → AwesomeScreen Doesn't Match Properly
Summary: AwesomeScreen Doesn't Match Properly → AwesomeScreen Doesn't Match Multiple Fields
Whiteboard: parity-desktop
This sounds like a dupe of bug 738961.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.