Hi ,
Do you still see this occurring in 4.12 Preview 4 (released earlier today)? I just tested our test case there and it appears to be working correctly. I also checked 4.11.2, and it was not working in that version. It looks like 4.12 should have this corrected for you.