Note: I implemented XWIKI-22339 in 16.10.3 and this caused this UI bug. On my own firefox development browser, I could not reproduce the bug.
I am testing on Chrome to provide a solution.