Context Navigation

Changes between Initial Version and Version 1 of Ticket #3670, comment 90

initial	v1
6	6	I think there are merits to both approaches. The first solution has little risk and provides developers to properly work around the issues they are having in core. However, it has been pointed out that hooking in the problematic function doesn't solve the bigger picture perfectly. The second solution appears to be what we would like tackle, but not without thorough testing. It is a much bigger lift.
7	7
8		I propose we address this ticket with the filter approach from ~~3670.2.diff~~ as to put a nail in the coffin of requiring plugin authors to hack at core. I'd then like to open a new ticket aimed at tackling the root of the problem as it relates to the way we escape XML.
	8	I propose we address this ticket with the filter approach from [attachment: 3670.2.diff] as to put a nail in the coffin of requiring plugin authors to hack at core. I'd then like to open a new ticket aimed at tackling the root of the problem as it relates to the way we escape XML.