Change Details

As far as I know, the reason for loading the site module in a separate request is that it needs to execute in global context, rather than in a standard module closure, but we can work around it by using $.globalEval. Regardless of whether or not that is the reason, let's figure out how to load it along with other modules, and save ourselves a request in the critical path. -------------------------- **Version**: 1.23.0 **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=27302 https://bugzilla.wikimedia.org/show_bug.cgi?id=63728

As far as I know, the reason for loading the site module in a separate request is that it needs to execute in global context, rather than in a standard module closure, but we can work around it by using $.globalEval. Regardless of whether or not that is the reason, let's figure out how to load it along with other modules, and save ourselves a request in the critical path. -------------------------- See also: * {T29302}

As far as I know, the reason for loading the site module in a separate request is that it needs to execute in global context, rather than in a standard module closure, but we can work around it by using $.globalEval. Regardless of whether or not that is the reason, let's figure out how to load it along with other modules, and save ourselves a request in the critical path. -------------------------- **Version**: 1.23.0See also: **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=27302 https://bugzilla.wikimedia.org/show_bug.cgi?id=63728 {T29302}