Closed Bug 821200 Opened 12 years ago Closed 9 years ago

Installing a packaged app with multiple entry points - wrong app icon and name appears on screen, entry point app icons do not show either

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jsmith, Unassigned)

References

Details

Build - Beta 12/12/2012
Device - Unagi

Steps:

1. Go to http://owapps.cloudfoundry.com
2. Select to install the packaged app with entry points
3. Confirm installation
4. Wait for installation to complete

Expected:

During download of the app, it's a bit unknown whether we should show the app itself or each entry point being downloaded. However, when download is complete, the entry point app icons and name should be present for that app.

Actual:

When download is complete, we show the name of the app overall, not multiple app icons and names to represent each entry point.
Can't seem to search bugzilla right now, but the decision to fix this bug is dependent on whether we decide to leave entry points on for v1.
blocking-basecamp: --- → ?
Peter Chris, do we support multiple entry points in V1 ?
blocking-basecamp: ? → -
Flags: needinfo?(pdolanjski)
Flags: needinfo?(clee)
Blocks: 820863
(In reply to dscravaglieri from comment #2)
> Peter Chris, do we support multiple entry points in V1 ?

Please keep this nomed at the moment until the contention in bug 820863 is resolved. If we won't fix that bug, then this is definitely going to have to be fixed.
blocking-basecamp: - → ?
Also - see bug 820863 for the disabling discussion. I'll add those folks to the needs info list.
Flags: needinfo?(pdolanjski)
Flags: needinfo?(clee)
Out of scope now for v1. Removing from nomination queue.
blocking-basecamp: ? → ---
This should be resolved for the vertical home screen, but since we're also removing support for entry points eventually, it's something that we probably don't need to fix.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.