Closed Bug 1038042 Opened 10 years ago Closed 10 years ago

Synced Tabs/Tabs from other devices are hard to find

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(firefox33 affected)

Status:
RESOLVED DUPLICATE of bug 1037527
Tracking Flags:
Tracking Status
firefox33 --- affected

People

(Reporter: gcp, Unassigned)

References

Details

Regression ~1 week old:

In the awesomebar, going to the "synced tabs/tabs from other devices" thingie, shows a list of all known systems, but the tabs are not listed. This is a Firefox for Android-only bug, desktop Nightly is still working fine.
Blocks: 899643
So apparently the devices are clickable, despite there being exactly 0 visual indication that they'll fold out.
tracking-fennec: --- → ?
status-firefox33: --- → affected
Component: Android Sync → General
Product: Android Background Services → Firefox for Android
Summary: Synced Tabs/Tabs from other devices not listing tabs, only devices → Synced Tabs/Tabs from other devices are hard to find
See comment https://bugzilla.mozilla.org/show_bug.cgi?id=899643#c31 and later. The visual indicators weren't landed because they weren't according to the UX design. The final UX design won't land until 34, so 33 is in a bad limbo state.
gcp, thanks for filing.  This was a regression from https://bugzilla.mozilla.org/show_bug.cgi?id=1003610; I did not intend to change the expanded property.  capella's going to land the indicators, or expand everything initially.  capella, can you dupe this bug to the one we already filed?
FYI I filed bug 1037527 last week to leave sections expanded by default, until we add expand/collapse indicators to the UI
That bug looks like it can track Firefox 33 so this one is redundant.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
tracking-fennec: ? → ---
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.