1092309 - [Everything.me] User can't remove preloaded smart collection apps in a custom smart collection

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

Description

[[:SalvadorR]]

Attachment: logcat_20141030_1619.txt

Description:
If user Adds a custom Smart Collection, user will not be able to remove preloaded smart collections contained in the new  custom smart collection
   
Repro Steps:
1) Update a Flame device to BuildID: 20141029001202
2) Add a new custom Smart Collection to Homescreen
3) Enter custom Smart Collection
4) Attempt to remove preloaded Smart Collection Apps 
  
Actual:
Can't remove preloaded Smart Collection Apps in a Custom Smart Collection
  
Expected: 
Can remove preloaded Smart Collections Apps
  
Environmental Variables:
Device: Flame 2.1 (319mb) KK Full Flash 
BuildID: 20141029001202
Gaia: eb0aab0f13c78c7ac378ad860e865c4b6eaf669f
Gecko: 318019f80a8e
Gonk: 6e51d9216901d39d192d9e6dd86a5e15b0641a89
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
  
Repro frequency: 3/3
See attached: Video, Logcat
http://youtu.be/NTxzZNR4vqk

Comment 1

[[:SalvadorR]]

This also occurs on Flame 2.0 and Flame 2.2

Result: User can't remove preloaded Smart Collection apps

Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141029000205
Gaia: 9f5b6f025e528fabfcc068782cb9b492cb51a7f9
Gecko: de8cfd54bf93
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 32.0 (2.0)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 2.2

Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141029040208
Gaia: 35e87ac4324f0f3abd93dcc70d61c9f37256a0f5
Gecko: 7e3c85754d32
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Comment 2

[Joshua Mitchell (Inactive)]

[Blocking Requested - why for this release]: This seems like pretty bad UX - users will expect something labeled as Custom to be Customizable

Comment 3

[Wayne Chang [:wchang]]

Rob,

I think this is expected given that smart collections are automatically generated collections based on user's keyword (the 'custom' here).

So this doesn't sound like a bug to me... but feel free to reopen and nominate if i misunderstood smart collections.

Comment 4

[Joshua Mitchell (Inactive)]

(In reply to Wayne Chang [:wchang] from comment #3)
> Rob,
> 
> I think this is expected given that smart collections are automatically
> generated collections based on user's keyword (the 'custom' here).
> 
> So this doesn't sound like a bug to me... but feel free to reopen and
> nominate if i misunderstood smart collections.

I could see how the pre-labeled smart collections would behave as such but the issue here is specific to the 'custom' one in which a user will expect to be able to add or delete content as they see fit.

Comment 5

[Tiffanie Shakespeare [:tif]]

UX triage - We believe smart collections are going away? NI Peter.

Thanks!

Comment 6

[Peter Dolanjski [:pdol]]

Yes, Smart Collections have been removed in 2.5.