MC-178909 is either erroneously marked as Resolved, or the bug has reappeared in the 6 years since, the screenshot and listed steps are enough to recreate this issue.
MC-178909 is either erroneously marked as Resolved, or the bug has reappeared in the 6 years since, the screenshot and listed steps are enough to recreate this issue.