Yes, the issue has been fixed.
Still happening in 1.14.2 pre-releases 1 and 2
MC-147740 and MC-151079 describe parts of my issue but not the full picture.
Yes, the issue has been fixed.