This bug migrated to the Web AppBuilder for ArcGIS. It is quite shame not to address it and move it to the new product.
I'm pretty sure this bug has been addressed in ArcGIS Online and the templates. I also ran a quick test using the Web App Builder and it looks fixed there as well. Do you have a test web map that still shows the problem?
It looks like the status is now Closed: Will Not be Addressed.