Steps: 1. Go to about:apps on Nightly Expected: about:apps should redirect to the myapps dashboard, including in the location bar. Actual: See screenshot. Missing stylesheets, appcache prompt is incorrect, and URL in the location bar isn't right.

Bringing the IRC discussion in here - not a blocker, as about:apps is likely not an entry point for users. The issue from what I understood in the IRC discussion was server-side, not client-side. I'll hold the discussion on whether to keep the code active or not until a discussion on Friday occurs about apps presentation in Firefox to determine a different question: "If we don't intend to fix this bug by first release of AITC, should we file and fix a bug to backout or pref off the code for about:apps?"

(In reply to Jason Smith [:jsmith] from comment #1) > Bringing the IRC discussion in here - not a blocker, as about:apps is likely > not an entry point for users. The issue from what I understood in the IRC > discussion was server-side, not client-side. I'll hold the discussion on > whether to keep the code active or not until a discussion on Friday occurs > about apps presentation in Firefox to determine a different question: > > "If we don't intend to fix this bug by first release of AITC, should we file > and fix a bug to backout or pref off the code for about:apps?" Jason, we are working on defining a simple App Management experience as the first AITC user interface, see the product page at https://wiki.mozilla.org/Features/Apps/AppsManagement Rather than spending a lot of time on the old about:apps, IMHO we should figure out how the App Management experience best this makes sense on Android.

(In reply to Bill Walker [:bwalker] [@wfwalker] from comment #2) > (In reply to Jason Smith [:jsmith] from comment #1) > > Bringing the IRC discussion in here - not a blocker, as about:apps is likely > > not an entry point for users. The issue from what I understood in the IRC > > discussion was server-side, not client-side. I'll hold the discussion on > > whether to keep the code active or not until a discussion on Friday occurs > > about apps presentation in Firefox to determine a different question: > > > > "If we don't intend to fix this bug by first release of AITC, should we file > > and fix a bug to backout or pref off the code for about:apps?" > > Jason, we are working on defining a simple App Management experience as the > first AITC user interface, see the product page at > https://wiki.mozilla.org/Features/Apps/AppsManagement > > Rather than spending a lot of time on the old about:apps, IMHO we should > figure out how the App Management experience best this makes sense on > Android. Right I agree. The concern I have is that we have code active that isn't working, and if we don't intend it to be an entry point and/or want to fix the issues surrounding it, then let's close off the code path entirely (pref off what exists).

We should fix this, no doubt. about:apps is useful for developers, if nothing else. My only contention is that it is not a blocker.

(In reply to Anant Narayanan [:anant] from comment #4) > We should fix this, no doubt. about:apps is useful for developers, if > nothing else. My only contention is that it is not a blocker. Here's an idea that I think could address both our perspectives - Could we pref about:apps off for FF 16? That way both perspectives being brought here are addressed (about:apps = not a priority & avoiding leaving code that kinda does not work active). Although leaving the hanging fruit of keeping the code active on any build while it's not working may not be a good idea, especially since this isn't a priority right now. Perhaps the better approach is to keep about:apps hidden behind a pref?

Let's talk post the AITC meeting on Tuesday about this with Bill (if he's available). I can probably clarify this better in person.

Dead component, closing bugs in it.