Closed Bug 596612 Opened 9 years ago Closed 9 years ago

tabs open on synced computers should be indicated in awesomelist results


(Firefox for Android Graveyard :: General, defect)

Not set



Tracking Status
fennec 2.0b2+ ---


(Reporter: madhava, Assigned: vingtetun)


(Whiteboard: awesomepanel)


(1 file, 1 obsolete file)

This is shown in this mockup:

When a user is searching in the awesomescreen, and an item in the list is a currently open tab on a remote browser, we should indicate that with an icon in the spot indicated.

The android theme mockups are a more up-to-date depiction of placement and style of this icon.
blocking2.0: --- → ?
blocking2.0: ? → ---
tracking-fennec: --- → ?
OS: Mac OS X → All
Hardware: x86 → All
Version: 1.9.2 Branch → Trunk
tracking-fennec: ? → 2.0b2+
Attached patch Patch (obsolete) — Splinter Review
I''ve decided to use the badge helper to do this, mostly because I was looking for a way to not slow down the awesome screen.
It could be not the best decision but I think it makes sense.
Attachment #477945 - Flags: review?(mark.finkle)
Comment on attachment 477945 [details] [diff] [review]

I like doing this in a delayed manner, but I think we should split it out from the badge system. Can you just add a separate remote badge check and method in the binding itself? I don't think we want add-ons to mess around with this badge.
Attached patch PatchSplinter Review
Attachment #477945 - Attachment is obsolete: true
Attachment #477959 - Flags: review?(mark.finkle)
Assignee: nobody → 21
Comment on attachment 477959 [details] [diff] [review]

Just move the remote badge code before the generic badge code. If I had to prioritize, I would say that the remote badges should become visible first. The generic badges might be time consuming.
Attachment #477959 - Flags: review?(mark.finkle) → review+
Whiteboard: awesomepanel → awesomepanel [fennec-checkin-postb1]
Comment on attachment 477959 [details] [diff] [review]

>+              // once we have check badges, check if the tab is in the remote list
>+              if (!Weave.Service.isLoggedIn)
>+                return;
>+              for (let i = 0; i < remoteItems.length; i++) {
>+                let remoteURI = remoteItems[i].uri;
>+                if (remoteURI) {
>+                  let itemHost =, null, null);
>+                  let remoteHost =, null, null);
>+                  if (itemHost.equals(remoteHost))
>+                    item.setAttribute("remote", "true");
>+                }

I am wondering how slow this will be. For people like me, the remoteItems array could be a few hundred items. Well need to keep an eye on this.
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: awesomepanel [fennec-checkin-postb1] → awesomepanel
Flags: in-testsuite?
Flags: in-litmus?
Flags: in-litmus? → in-litmus?(tchung)
Flags: in-litmus?(tchung) → in-litmus+
Verified fix on Mozilla/5.0 (Android; Linux armv71; rv:2.0b13pre) Gecko/20110317 Firefox/4.0b13pre Fennec/4.0b6pre
You need to log in before you can comment on or make changes to this bug.