Context Navigation

Changes between Initial Version and Version 1 of Ticket #37110, comment 157

initial	v1
14	14	@azaozz If a plugin or theme adds an enqueue for jQuery migrate, they are acknowledging that they are aware of the problem, researched why it happened, and made a purposeful change to temporarily fix the issue. If they then do not update the code in the next 3-5 months before 5.6, then that's on them at that point, in my opinion. If they do update their code, then in 5.6 when `jquery-migrate` is updated to the latest version, then there would be no problems as Core intends to re-add migrate as an enqueue. The only difference is that it will be for migrating to a newer version of jQuery.
15	15
16		As for creating a plugin or polyfill to solve this (other than [attachment:"37110-add-dependency.diff"]), I am still of the opinion that creating a custom wheel here should be avoided. If it's decided that there is enough potential for breakage that action should be taken, then my vote would be to revert [48323] and use a more aggressive outreach program (emailing plugin and theme authors directly, and often).
	16	As for creating a plugin or polyfill to solve this (other than [attachment:"37110-add-dependency.diff"]), I am still of the opinion that creating a custom wheel here should be avoided. If it's decided that there is enough potential for breakage that action should be taken, then my vote would be to revert [48323] and use a more aggressive outreach program (emailing plugin and theme authors directly, and often), and retry again in 5.6.