I share the frustration for this long-standing issue, but there is a difference between tracking an issue and being able to reproduce it. The former comes before the latter. Now that there are documented reproduction for the devs, they can fix it. Mind you, my level of frustration here is that it seems like this is one of the many items that should have been addressed before GA. But it didn't happen, so we're slotted in the general bugfix cycle.