Indeed, the problem persists in version 3.2. I will mention it in the Gitlab issue as well as in the 3.2 feedback.
I feel relatively powerless to help resolve this issue. Perhaps @Manoj can guide us on how to call on a developer to take charge of this issue? (Still awaiting stage at present)…
Thank you beforehand!