Bug 918174 made the quick and easy fix to avoid style recomputations when lazy loading CSS in contacts. We should spend more time, however, to determine if the app can be refactored to better defer these loads. For example, can the progress.css be deferred until the first time a progress overlay is needed, etc. In addition, we should investigate using scoped styles where possible to minimize the recomputations that are needed when the style sheets are loaded.

It does seem that bug 918174 regressed opening a single contact via web activity (e.g. from call log). We may want to prioritize this for 1.2. Comms team, what do you think? Are you open to this kind of refactoring given the other work going on at the moment?

my advice here is to backout bug 918174. Major refactoring work should happen in 1.3 and not in 1.2

(In reply to Jose M. Cantera from comment #2) > my advice here is to backout bug 918174. Major refactoring work should > happen in 1.3 and not in 1.2 Ok. I'll do the backout. Are you open to an intermediate solution that moves the CSS loads around without too much refactoring? (I know that's hard to answer without seeing patches...)

I'm open to patches provided the demosntrate a clear performance win

So bug 918174 was backed out, but then I investigated the regression and realized it was not actually there. So in the end bug 918174 did land. Leaving this bug open to track possibly refactoring the CSS loading in the future. Dropping koi? nom based on comment 2.

Updating title to reflect that this is more about refactoring the style sheets to improve load times.

are we going to nom this for v1.3?

(In reply to Jose M. Cantera from comment #7) > are we going to nom this for v1.3? It sounds like that may be a good idea along with potentially other perf related refactoring. Is 1.3 a good time to do that? I guess nom'ing is the way to answer that. Thanks!

fxos-perf-triage: David, theses changes would be significant for the Contacts app so the Comms Apps team should make the call on whether to 1.3+ this. Please assign someone and decide whether to + or - this for 1.3.

Jose, what's your advice on this ?

I think we should definetely work on this on v1.3

triage: not blocking 1.3 release. please land in master when ready. thanks

Based on the investigation Doug did in bug 996776 I think we can probably mark this WONTFIX as well.