Agree. We should not hold our breath.
But since a "server-side" update introduced the bug, there should be ownership on their side to "do no harm" to the established customer based.
From a forum posting, I discovered a workaround that works for what I want to do. Hopefully others can discover the same workaround.