Yup, the bug is still there in 10.2, and still no response from Blizzard on this since it resurfaced back in September.
For reference, below is Blizzard Blue’s acknowledgement of the issue back in May, and what appears to be a genuine desire to see it fixed … to the point where it did get fixed. But why they have gone radio silent since it resurfaced? I have no idea.
Obviously the fix has been documented by internal ticketing and CI build tools, so it shouldn’t take a big effort to track it down and reimplement … I mean, any solutions architect, senior developer, release manager, etc. should be able to do this in their sleep … Come on blizz.