995306 - [email] Consider using location fragments for activities

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[James Burke [:jrburke]]

In IRC it came up that SMS uses fragment IDs for activity entry points:

https://github.com/mozilla-b2g/gaia/blob/a55eb67d0659327a8e4b64099fc76a634823fecd/apps/sms/manifest.webapp#L48

The camera app was seeing about a 100ms delay by using the mozPendingMessage route, so this might be useful for email too.

Keep in mind how to balance it with possibly using pushState and URL changes for card navigation. It may be that bug 935750 now allows restoration of URL history state changes if the app is killed.

Comment 2

[Nancy]

(In reply to James Burke [:jrburke] from comment #0)
> In IRC it came up that SMS uses fragment IDs for activity entry points:
> 
> https://github.com/mozilla-b2g/gaia/blob/
> a55eb67d0659327a8e4b64099fc76a634823fecd/apps/sms/manifest.webapp#L48
> 
> The camera app was seeing about a 100ms delay by using the mozPendingMessage
> route, so this might be useful for email too.
> 
> Keep in mind how to balance it with possibly using pushState and URL changes
> for card navigation. It may be that bug 935750 now allows restoration of URL
> history state changes if the app is killed.

Hi James,

The bug can reproduce on 2.0.
There is a lot of difference between SMS and Email. Could you please give more detailed information about activity fragment IDs?

Thanks

Comment 3

[James Burke [:jrburke]]

URL fragment IDs are the #something on the end of a URL. SMS uses them in their manifest.webapp to indicate state to the app so they can start some of that state-specific work without waiting for a mozSetMessageHandler listener to fire.

For email, we just wait for the mozSetMessageHandler to fire to construct the UI, since it contains data to complete the final UI. However, we could go ahead and set up the basic card UI without the data using fragment IDs.

This ticket is about considering that adjustment in email, and not around a specific performance target that was failing, it was just something nice to have. It is not currently scheduled for a fix, although I did want to try some experiments around it for 2.2, but at the moment this is lower priority than the scheduled/planned work for 2.2.

If you are seeing a specific issue or are just concerned about app startup from an activity for email, it would be good to get more context about that. 

As far as the scope of changes to accomplish the goal of this ticket, the changes would be invasive enough that we would not want to push the changes to 2.0 or 2.1, without a clear "the app does not run/is broken" bug scenario.

Comment 4

[BMO Automation]

Firefox OS is not being worked on