The confirmed bug shown in my video here is still present in 2.03 and still not filed as “known issue”