-
- Downloads
Bug 1385396 - Cache early setExperimentActive calls r=gfritzsche
Calling setExperimentActive too early during startup can change the order of some initialization. setExperimentActive probably shouldn't have this kind of effect, so simply cache early calls to it until gGlobalEnvironment has been initialized through other functions. Additionally, I am speculatively including work to ensure that setExperimentInactive and getActiveExperiments have the same behavior, while remaining correct by working from the same cache that setExperimentActive uses. MozReview-Commit-ID: IlzT1J0o6gK --HG-- extra : rebase_source : b39b8d7e7b0970b520ce3f63af9750846d08b0eb
Please register or sign in to comment