It was already present in 4.4.0. It was not fixed in 4.4.1 preview. I haven’t seen any indication if it will make the final 4.4.1 or not. And its been driving me nuts.
It was already present in 4.4.0. It was not fixed in 4.4.1 preview. I haven’t seen any indication if it will make the final 4.4.1 or not. And its been driving me nuts.