Adding the first filter/action in an earlier priority during a later priority causes the earlier priority to run (last)
|Reported by:||devesine||Owned by:|
During testing of #21169, it occurred to me that http://core.trac.wordpress.org/ticket/5338#comment:1 might present a problem with each rather than next/current, but that turns out not to be the case. Instead, this exposed a different bug:
If you add a new filter at priority 9, when priority 9 did not previously have any filters, during the priority 10 execution, the priority 9 filter will run (!) after all other priorities (since the filters are not resorted after each priority).
(Generally, if you add an earlier priority that did not previously have any filters during a later priority...)
The attached unit test demonstrates this behavior.