Context Navigation

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

initial	v1
2	2	> I guess, then, that switching WordPress itself to native JS and only enqueuing it if it's listed as a dependency anywhere may be a way to take a step forward in core.
3	3
4		Right. This is the best way to move to native JS. It is fully backwards compatible, and can be done at any time (not dependent on other changes in core). This is ~~pretty~~ straightforward for wp-admin as it [https://make.wordpress.org/core/handbook/best-practices/browser-support/ supports only newer browsers]. Would be more problematic for the front-end as generally "all browsers that are currently in use" should be supported.
	4	Right. This is the best way to move to native JS. It is fully backwards compatible, and can be done at any time (not dependent on other changes in core). This is more straightforward for wp-admin as it [https://make.wordpress.org/core/handbook/best-practices/browser-support/ supports only newer browsers]. Would be more problematic for the front-end as generally "all browsers that are currently in use" should be supported.
5	5
6	6	> If there is no major significance to the inline version number, why not just change it...