Closed Bug 841760 Opened 12 years ago Closed 12 years ago

Lazy load more things in the settings app.

Categories

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

x86_64
Linux
defect
Not set
normal

Tracking

(blocking-b2g:tef+, firefox18+, b2g18 fixed, b2g18-v1.0.1 fixed)

RESOLVED FIXED
blocking-b2g tef+
Tracking Status
firefox18 + ---
b2g18 --- fixed
b2g18-v1.0.1 --- fixed

People

(Reporter: vingtetun, Assigned: jhammink)

References

Details

(Keywords: verifyme, Whiteboard: [FFOS_perf][target 28/2] QARegressExclude)

Attachments

(3 files, 2 obsolete files)

Attached patch CSS PatchSplinter Review
This will be divided in 2 parts. One for the css, one for the js.
Attachment #714378 - Flags: review?(etienne)
That should probably not block a *gecko* bug :P
No longer blocks: 834622
Attached patch JS PartSplinter Review
Spoiler: with the "optimize" build step activated and the wing in the right direction this patch on top of the CSS one get's us a settings startup time < 1sec :)
Attachment #714483 - Flags: review?(21)
s/wing/wind
Comment on attachment 714378 [details] [diff] [review] CSS Patch Review of attachment 714378 [details] [diff] [review]: ----------------------------------------------------------------- ::: apps/settings/js/settings.js @@ +132,5 @@ > + // activate all stylesheets > + var stylesheets = panel.querySelectorAll('link'); > + for (var i = 0; i < stylesheets.length; i++) { > + var href = stylesheets[i].getAttribute('href'); > + if (document.head.querySelector('link[href="' + href + '"]')) wouldn't mind some curly braces
Attachment #714378 - Flags: review?(etienne) → review+
Etienne will merge it so assigning to him :) (thanks!)
Assignee: nobody → etienne
Should this be uplifted to v1.0.1?
Comment on attachment 714703 [details] [diff] [review] Part 1 rebased to 1.0.1 Looks like these patches conflict a bit, so I'll let you guys sort it out :).
Attachment #714703 - Attachment is obsolete: true
Should be pretty safe, mostly refactoring & renaming.
blocking-b2g: --- → tef?
blocking-b2g: tef? → -
Apologies for the churn. Verified with akeybl that perf bugs we want to land should be nominated for TEF+ vs simply asking for approval.
blocking-b2g: - → tef?
Attached patch Patch - delay more things. (obsolete) — Splinter Review
There is no need to block the page load on those scripts - let's show the page content as soon as possible.
Attachment #716416 - Flags: review?(etienne)
Comment on attachment 716416 [details] [diff] [review] Patch - delay more things. Review of attachment 716416 [details] [diff] [review]: ----------------------------------------------------------------- Looks like it's breaking stuffs. Let me know if you need somebody else to debug it.
Attachment #716416 - Flags: review?(etienne) → review-
Assignee: etienne → 21
blocking-b2g: tef? → tef+
Whiteboard: [FFOS_perf] → [FFOS_perf][target 28/2]
We'll have to resolve this in a future release. Too much risk a couple of days before being totally code frozen for v1.0.1.
blocking-b2g: tef+ → -
Attached patch PatchSplinter Review
Sigh. The regression are because I forgot a .js at the end of connectivity.js...
Attachment #716416 - Attachment is obsolete: true
Attachment #717960 - Flags: review?(etienne)
Attachment #717960 - Flags: review?(etienne) → review+
Since we are tef+ some bugs that does not change much I feel like a few hundreds of milliseconds worth tef+'ing it.
blocking-b2g: - → tef?
blocking-b2g: tef? → tef+
Commit ef60a5e50ef39c7fd15cb07dbdfaa1a23cd7d747 does not apply to v1-train or v1.0.1. This means that there are merge conflicts which need to be resolved. If there are dependencies that are not approved for branch landing, or have yet to land on master, please let me know If a manual merge is required, a good place to start might be: cd gaia git checkout v1-train git cherry-pick -x -m1 ef60a5e50ef39c7fd15cb07dbdfaa1a23cd7d747 <RESOLVE MERGE CONFLICTS> git checkout v1.0.1 git cherry-pick -x $(git log -n1 v1-train)
Actually, there were 3 commits on master : 2f86aad75e00ffd578f8f5245fcde81af2ef516d bb65b9c82bade667a07bc699bdbd5c80daa44df3 ef60a5e50ef39c7fd15cb07dbdfaa1a23cd7d747 It would make sense to land the first two at once, and the third one separatly, because they landed at 10 days interval. It still doesn't apply cleanly yet but I'm on it.
This doesn't apply at least because of Bug 832082 that should (maybe) land on v1-train/v1.00.1 too, so I'm waiting for an answer there first.
v1-train: ad21b1adce731abe47bce6518d29b272dbb8faa3 v1-train: 07b7f216a9a7d5a0a7acaa576a950b996158d1d8 v1-train: 7d1cdb5a11fbd47ec1d8ac131b9330120e293f60 On v1.0.1, only 2f86aad75e00ffd578f8f5245fcde81af2ef516d applies cleanly, but I won't uplift anything there yet because I assume we want these atomically applied.
Flags: needinfo?(felash)
Marking v1.0.1 as affected so we can track this
v1.0.1: 8164523544e500e388d85d546bc51672b8e0d6b0 (pushed the first one only by error, doing the others right now)
Flags: needinfo?(felash)
v1.0.1: 37ad710061197f5818fa6afd010b698232dda7c9 v1.0.1: 60cade2203b8237ce3d7aedcd759a537029eb8cb
does not make sense to create a regression issue.
Flags: in-moztrap-
Can you please provide steps to verify this fix - as we will blackbox test from the UI?
Nothing special, just check that everything works ok, including navigating to subpanels and manipulating controls, eg changing the language.
Whiteboard: [FFOS_perf][target 28/2] → [FFOS_perf][target 28/2] QARegressExclude
Cannot verify, need specifics on what exactly was changed so we know what to check.
Check that the settings app work as per testruns and smoketests.
Assignee: 21 → jhammink
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: