Context Navigation

Changes between Version 2 and Version 3 of Ticket #21170, comment 183

v2	v3
4	4	I actually think this is the opposite. The greatest strength of wp.hooks is that it is "above" any/all modules, packages, components, libraries, etc. and enables easy interoperability for all of them. Each library has its own native signalling methods that usually fit internal use best. We can, of course, enable wp.hooks to be used internally in modules, but thinking this will diminish its best user case: make it possible to use any library at any time with all plugins.
5	5
6		I do realize this is somewhat controversial, but then we are solving a problem the great majority of JS projects never encounter: how to facilitate interoperability of several external components at the same time. Even the browser's events API is only targeted at single JS "source" and is not adequate when several different libraries try to cooperate and have to use the same events.
	6	I do realize this is somewhat controversial, but then we are solving a problem the great majority of JS projects will never encounter: how to facilitate interoperability of several external components at the same time. Even the browser's events API is only targeted at single JS "source" and is not adequate when several different libraries try to cooperate and have to use the same events.