Closed
Bug 976858
Opened 11 years ago
Closed 11 years ago
Installing a social app is displayed twice in home screen
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: pensacola_m2000, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131028112629
Steps to reproduce:
FF OS version 1.4.0.0 commit no from Feb 25, 2014
Install latest version of Facebook.
Check the home screen
Actual results:
The app shortcut is displayed twice, once in Social group from homescreen and then once again on homescreen
Expected results:
The app should be installed.
Comment 1•11 years ago
|
||
That's not a bug.
Smart Collections (the groups on the homescreen) are not designed to be like folders.
All installed apps are always located on Homescreen and in other Smart Collections they've been added to manually or automatically.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Ran Ben Aharon (Everything.me) from comment #1)
> That's not a bug.
> Smart Collections (the groups on the homescreen) are not designed to be like
> folders.
> All installed apps are always located on Homescreen and in other Smart
> Collections they've been added to manually or automatically.
From UX point of view I would like to have the option to remove the app shortcut from homescreen without being removed from Smart Collections too. For example SoundCloud is displayed 3 times : Music and Social Smart Collections and then on homescreen too. Is this possible now or could be?
Flags: needinfo?(ran)
Comment 3•11 years ago
|
||
It's currently not possible. It's a conscious decision made by Mozilla UX.
There were quite a few discussions and bugs opened on this subject (i.e. Bug 875303)
Flags: needinfo?(ran)
Reporter | ||
Comment 4•11 years ago
|
||
okay,marking the bug as verified invalid.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•