Context Navigation

Changes between Version 1 and Version 2 of Ticket #12009, comment 127

v1	v2
3	3	> I’m confused because previously [https://core.trac.wordpress.org/ticket/12009?replyto=125#comment:86 you said] that "support for concatenation would not be a priority and probably won't be necessary.
4	4
5		Yea, sorry, I didn't explain that well at all. The reasons I think support for concatenation is not needed in the first iteration (this patch) is because only default core scripts can be concatenated and only in wp-admin. As there are no default scripts that are (can be) loaded with `async` or `defer`, adding concatenation support seems an overkill. If eventually there are enough (new) core scripts that are loaded with `async` or `defer` by default, it seems concatenation can be added as that dramatically speeds up page load times on HTTP/1.2.
	5	Yea, sorry, I didn't explain that well at all. The reasons I think support for concatenation is not needed in the first iteration (this patch) is because only default core scripts can be concatenated and only in wp-admin. As there are no default scripts that are (can be) loaded with `async` or `defer`, adding concatenation support now seems an overkill. If eventually there are enough (new) core scripts that are loaded with `async` or `defer` by default, it seems concatenation can be added as that dramatically speeds up page load times on HTTP/1.2.
6	6
7	7	> Actually, being able to transition applicable core scripts to use a delayed strategy is specifically what we want to explore once this gets merged (e.g. `comment-reply`).