As per the src; Qt assumes that all resize requests will succeed (and in turn, apparently, "proactively" resizes child windows for such requests; it's not clear if this is because of or even related to the noted issue; it may just be how Virtualbox commands Qt5 to behave in this case). This leads to very broken behavior and unusable applications where this assumption is invalid; for a library like Qt, it's never actually valid (as acknowledged by the FIXME: comment).
This has most recently shown its face with the Virtualbox project, exposed by i3 and other window managers, though tiling window managers seem to make use of this protocol more than most. The Virtualbox bug report has some good details; the i3 report has good details on the compounding effects of such an issue.
|For Gerrit Dashboard: QTBUG-57608|
|198719,10||Ensure all platforms send geometry events if request was not fulfilled||dev||qt/qtbase||Status: MERGED||+2||0|
|201489,3||Fix Q(Quick)Window on eglfs||dev||qt/qtbase||Status: MERGED||+2||0|
|217683,3||Fix resize event flood when moving windows with High DPI scaling||5.10||qt/qtbase||Status: MERGED||+2||0|