Thanks Lucas. Indeed I could not reproduce on 15.x either but could on 14.10.16. Weird So this means the bug was corrected in 15 . x, right? This means we can mark it as fixed once we identify the version that contains the fix? !Screenshot from 2023-12-20 15-58-33.png|thumbnail! |
|