Context Navigation

Changes between Initial Version and Version 1 of Ticket #21170, comment 133

initial	v1
12	12	> I'm in favor of requiring that core JS filters always have a namespace or function name, but not so sure about making these mandatory for plugins. I think it would add a significant amount of friction for a fairly minor use case.
13	13
14		Then we will have many hook that are removable and some that are not? Don't think "partial support for removing actions and filters" is a good thing. Having said that, there may be a need for non-removable hooks, both for core and plugins. However if we are going to implement that I'd ~~prefer to see it as another arg rather than as optional namespace~~, mostly for clarity/readability.
	14	Then we will have many hook that are removable and some that are not? Don't think "partial support for removing actions and filters" is a good thing. Having said that, there may be a need for non-removable hooks, both for core and plugins. However if we are going to implement that I'd rather see it as another arg instead of an optional "namespace", mostly for clarity/readability.
15	15
16	16	> Either way, PHP parity is not something we should necessarily strive for...