Just verified this is fixed in our internal Release branch. It did not make it into 4.11 Preview 1, but I would anticipate it being fixed in following Preview build.
Just verified this is fixed in our internal Release branch. It did not make it into 4.11 Preview 1, but I would anticipate it being fixed in following Preview build.