Closed
Bug 1031084
Opened 12 years ago
Closed 11 years ago
"Save to homescreen" is still displayed even though this app is already on the homescreen
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(b2g-v1.4 unaffected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| b2g-v1.4 | --- | unaffected |
| b2g-v2.0 | --- | affected |
| b2g-v2.1 | --- | affected |
| b2g-v2.2 | --- | fixed |
People
(Reporter: jlorenzo, Assigned: crdlc)
References
Details
(Whiteboard: [systemsfe])
Attachments
(1 file, 1 obsolete file)
STR
1. Open a collection
2. Add an e.me app to the homescreen
3. Long press this e.me again
Actual result
Context menu is displayed with that entry: "Save to homescreen"
Expected result
This entry should be hidden. Right now, tapping it leads you to the Edit bookmark page. If you modify it, changes are made on the homescreen but not inside the Collection, which is confusing.
| Reporter | ||
Comment 1•12 years ago
|
||
Confusing UX.
blocking-b2g: --- → 2.0?
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking+]
status-b2g-v2.0:
--- → affected
Comment 2•12 years ago
|
||
I don't understand the bug here. Can you rephrase and/or provide a video?
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking+] → [VH-FL-blocking-][VH-FC-blocking?]
Flags: needinfo?(jlorenzo)
| Reporter | ||
Comment 4•12 years ago
|
||
STR:
1. Enter a Smart Collection
2. Long press an app suggestion from e.me
3. Save this app to the homescreen as bookmark
4. Back in the Smart Collection, long press the same app suggestion
Result: You'll see the same context menu as in step 2. This context menu contains an entry called "Save to homescreen" which is weird because the app has just been saved to the homescreen.
Moreover, if you tap "Save to homescreen" it actually leads you to the "Edit bookmark" page. And if you edit it (by remove some characters), you'll only edit the app on the homescreen and not the one you pressed in step 4.
Comment 5•12 years ago
|
||
FWIW - we do this everywhere, and I'm assuming it's been this way for a long time. In the browser, or search app the link is always "Add to home screen", but if you've already added it, you're just taken to the edit screen.
It's certainly not the best UX, but I don't think we'd block on it given that it's been this way forever.
| Reporter | ||
Comment 6•12 years ago
|
||
Got it.
blocking-b2g: 2.0? → ---
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking-]
| Assignee | ||
Comment 7•12 years ago
|
||
We could do it but I think that solutions are risky when the bug is not so bad . We would have two approaches:
1) We could check if the bookmark is already stored in the system or not by means of BookmarkDatabase.get method importing the library and adding the access to the datastore in collection app.
2) Or adding an IAC message to know if a bookmark exists or not in the bookmark app
Comment 8•12 years ago
|
||
Does this same problem occur on 1.4 w/the old e.me search implementation?
Keywords: qawanted
| Assignee | ||
Comment 9•12 years ago
|
||
In 1.4 version, bookmarks and collections live in the homescreen app so when an evme-app was already bookmarked a message was displayed [1] because ev.e code asked to home, is this bookmark on the grid? If we have to support the same behavior we have to follow some approach explained in comment 7.
[1] https://github.com/mozilla-b2g/gaia/blob/master/apps/homescreen/locales/homescreen.en-US.properties#L70
Comment 10•12 years ago
|
||
This issue does NOT repro as written above on Flame 1.4. When attempting to add an app a second time the user is shown a prompt stating: "XX was already added to Home Screen"
Device: Flame 1.4
BuildID: 20140630000201
Gaia: aa896d5db1b4929f3bf31a0f4bb7de50530222a8
Gecko: 8cba60bc12ef
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-] → [VH-FL-blocking-][VH-FC-blocking-] [QAnalyst-Triage?]
status-b2g-v1.4:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Comment 11•12 years ago
|
||
But the issue did reproduce in the browser I assume? I don't think we actually know what the expected behavior of this should be. I assume we want to change the text to say something about editing the bookmark?
Adding a ni? on ux for expected behavior.
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 12•12 years ago
|
||
Flagging Rob while Jacqueline is out. I believe the expected behavior is "XX was already added to Home Screen".
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(rmacdonald)
Comment 13•12 years ago
|
||
(In reply to Stephany Wilkes from comment #12)
> Flagging Rob while Jacqueline is out. I believe the expected behavior is "XX
> was already added to Home Screen".
As a dialog after you click the button, or as a replacement for the button? Also wanted to verify that this should work the same from rocketbar, and the browser.
| Assignee | ||
Comment 14•12 years ago
|
||
I completely sure that when you tried to bookmark some web from browser app, the message was not displayed. Only from ev.me collections in 1.4
(In reply to Kevin Grandon :kgrandon from comment #13)
> (In reply to Stephany Wilkes from comment #12)
> > Flagging Rob while Jacqueline is out. I believe the expected behavior is "XX
> > was already added to Home Screen".
>
> As a dialog after you click the button, or as a replacement for the button?
> Also wanted to verify that this should work the same from rocketbar, and the
> browser.
Updated•12 years ago
|
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-] [QAnalyst-Triage?] → [VH-FL-blocking-][VH-FC-blocking-] [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Updated•12 years ago
|
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-] [QAnalyst-Triage+] → [VH-FL-blocking-][VH-FC-blocking-][QAnalyst-Triage+][lead-review+]
Comment 15•12 years ago
|
||
(In reply to Jason Smith [:jsmith] - PTO 7/14 - 7/18 from comment #8)
> Does this same problem occur on 1.4 w/the old e.me search implementation?
In v1.4 (and before)
--------------------
E.me displays a "Save to homescreen" contextmenu option for already-saved web results, but then shows an "Already added to homescreen" message.
The browser app also shows the "Save to homescreen" contextmenu entry but does not show the "Already added message"
In 2.0
------
Search, Browser and Collection apps are all using the 'save-bookmark' activity handled by the bookmark app.
All apps show an 'Add to Homescreen' contextmenu entry to an already saved bookmark (Collection actually shows 'Save to Homescreen' which we may want to change for consistency).
Changing the summary since this issue applies also to the Browser and Search apps.
An easy "fix" can be to rephrase 'Add/Save to Homescreen' in all relevant apps.
Summary: [Collection] "Save to homescreen" is still displayed even though this app is already on the homescreen → "Save to homescreen" is still displayed even though this app is already on the homescreen
Comment 16•11 years ago
|
||
The patch changes 'Save to Homescreen' to 'Add to Homescreen' in the collection app to match the phrasing in other apps.
Attachment #8460890 -
Flags: review?(kgrandon)
Comment 17•11 years ago
|
||
Comment on attachment 8460890 [details] [review]
Pull Request
Hey, it looks like you have some git troubles =(
Can you try rebasing? I think somehow you picked up another merge.
Attachment #8460890 -
Flags: review?(kgrandon)
Comment 18•11 years ago
|
||
Comment on attachment 8460890 [details] [review]
Pull Request
(In reply to Amir Nissim (:amirn) from comment #16)
> Created attachment 8460890 [details] [review]
filed bug 1043216 for the text changes in the collection app
Attachment #8460890 -
Attachment is obsolete: true
Comment 19•11 years ago
|
||
Changing the component per comment 15.
This applies to Browser, Search and Collections apps.
Component: Gaia::Everything.me → Gaia
Comment 20•11 years ago
|
||
NI'ing Francis to consider as part of system browser spec.
Flags: needinfo?(rmacdonald) → needinfo?(fdjabri)
Comment 21•11 years ago
|
||
(In reply to Cristian Rodriguez (:crdlc) PTO: 7/28 -> 8/18 from comment #14)
> I completely sure that when you tried to bookmark some web from browser app,
> the message was not displayed. Only from ev.me collections in 1.4
>
> (In reply to Kevin Grandon :kgrandon from comment #13)
> > (In reply to Stephany Wilkes from comment #12)
> > > Flagging Rob while Jacqueline is out. I believe the expected behavior is "XX
> > > was already added to Home Screen".
> >
> > As a dialog after you click the button, or as a replacement for the button?
> > Also wanted to verify that this should work the same from rocketbar, and the
> > browser.
My preferred solution would be not to show the "Add to Home Screen" option if the item is already on the Home Screen. This would apply across smart collections, search results and the browser.
Flags: needinfo?(fdjabri)
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
| Assignee | ||
Comment 22•11 years ago
|
||
thanks guys
Attachment #8481219 -
Flags: review?(kgrandon)
Attachment #8481219 -
Flags: review?(amirn)
Comment 23•11 years ago
|
||
Added comments on Github.
The patch does not cover the browser app, should we file another bug?
| Assignee | ||
Comment 24•11 years ago
|
||
I think so, the patch implements the behavior that we had in 1.x (ev.me/homescreen now search/homescreen)
(In reply to Amir Nissim (:amirn) from comment #23)
> Added comments on Github.
> The patch does not cover the browser app, should we file another bug?
| Assignee | ||
Comment 25•11 years ago
|
||
Addressed comments, thanks
(In reply to Amir Nissim (:amirn) from comment #23)
> Added comments on Github.
> The patch does not cover the browser app, should we file another bug?
| Assignee | ||
Comment 26•11 years ago
|
||
Any update here from reviewers?
Comment 27•11 years ago
|
||
Comment on attachment 8481219 [details]
Github pull request
Looks good. Thanks Cristian :)
Attachment #8481219 -
Flags: review?(amirn) → review+
Comment 28•11 years ago
|
||
looks like the new tests are failing :(
TEST-UNEXPECTED-FAIL | collection/test/unit/contextmenu_test.js | contextmenu > clicking an icon not bookmarked - TypeError: BookmarksDatabase.get(...).then(...) is undefined (app://collection.gaiamobile.org/js/contextmenu.js?time=1409661771758:124)
TEST-UNEXPECTED-FAIL | collection/test/unit/contextmenu_test.js | contextmenu > clicking an icon not bookmarked - expected false to be truthy
TEST-UNEXPECTED-FAIL | collection/test/unit/contextmenu_test.js | contextmenu > "before each" hook - Attempted to wrap show which is already stubbed
Flags: needinfo?(crdlc)
Comment 29•11 years ago
|
||
Comment on attachment 8481219 [details]
Github pull request
I'm fine with Amir's review here, but please update the tests. Thanks!
Attachment #8481219 -
Flags: review?(kgrandon)
| Assignee | ||
Comment 30•11 years ago
|
||
Thanks a lot, I gonna address it
(In reply to Amir Nissim (:amirn) from comment #28)
> looks like the new tests are failing :(
>
> TEST-UNEXPECTED-FAIL | collection/test/unit/contextmenu_test.js |
> contextmenu > clicking an icon not bookmarked - TypeError:
> BookmarksDatabase.get(...).then(...) is undefined
> (app://collection.gaiamobile.org/js/contextmenu.js?time=1409661771758:124)
> TEST-UNEXPECTED-FAIL | collection/test/unit/contextmenu_test.js |
> contextmenu > clicking an icon not bookmarked - expected false to be truthy
> TEST-UNEXPECTED-FAIL | collection/test/unit/contextmenu_test.js |
> contextmenu > "before each" hook - Attempted to wrap show which is already
> stubbed
Flags: needinfo?(crdlc)
| Assignee | ||
Comment 31•11 years ago
|
||
I have seen the problem, I added a mistake with the latest changes once addressed Amir's comment hehehe. Updating right now and waiting for green. Thanks guys
| Assignee | ||
Comment 32•11 years ago
|
||
Merged in master:
https://github.com/mozilla-b2g/gaia/commit/a29ac6b1222c8367c5fb3a15ac238d13b3bda696
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•11 years ago
|
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•