Context Navigation

Changes between Version 1 and Version 2 of Ticket #32544, comment 10

v1	v2
3	3	The [https://core.trac.wordpress.org/attachment/ticket/32544/32544.diff current patch] pretends that plugin developers, start using that logic to permit a full display of all unfiltered mime types for any use-case that is not even clear. But this is not what the reporter is asking for: he wants full-access regardless of the decisions of individual plugin developers, to restructure (and potentially generate security concerns) the whole function, so user filtering can be completely bypassed on call.
4	4
5		On top of this, the john of 10 years ago, believed that this was a `good-first-bug` which is not (in fact, as @ipm-frommen I'm also doubting if implementing the enhancement in this report is a ~~good idea at all~~)
	5	On top of this, the john of 10 years ago, believed that this was a `good-first-bug` which is not (in fact, as @ipm-frommen I'm also doubting if implementing the enhancement in this report is a `good-idea-at-all`)
6	6
7	7	Personally, I would preemptively consider this a `close` candidate for `wontfix` unless the reporter (unlikely, 10 years later) provides additional information about the full use-case (not just the flawed piece of code in a recursive endless loop that was provided in the OP)