Bug involving the default detonate mines button, and automation & detonate mines support gems

When automation support gem and detonate mines skill gem are linked:

1) If the automation gem is socketed before the detonate mines gem in the socket trigger order, then the default detonate mines "popup" will not appear, and the keybind for the default detonate mines does not work. This happens whether automation is turned on or off.

2) If these gems are moved into different sockets so that detonate mines comes first in the socket trigger order, then the default detonate button will start appearing again as expected when a mine is thrown.

3) There is another part of this bug as well. If "bugged" mines are created when the automation and detonate gems are in the "wrong" order, any new mines that are thrown while the bugged mines still exist will inherit the bug too (including mines that are created when the automation and detonate gems in the "correct" order, which can be done by quickly moving the gems to different socket while the bugged mines exist). Meaning, all active mines and all new mines created while a bugged mine exists must despawn or be detonated in order for the default detonate button to appear as expected upon a non-bugged mine being thrown.

I tested this behavior with all the variants of mines and it is consistent with all of them - pyroclast mine, icicle mine, high impact mine, blastchain mine, and locus mine.

And, by "trigger order" I am referring to this: https://www.poewiki.net/wiki/Trigger#Trigger_order