It’s still marked as “To Do”, however, it’s not listed as a fix version target of 4.11, so without that, it’s not going to show on the list of known issues for 4.11 that are being worked toward. I just checked in our internal build of 4.12 (CL-2894512) and this behavior is still the same. So, with that said I don’t have a timeframe for when this will be addressed.