As far as I was concerned this bug was already fixed in:-
0.52.1-1ubuntu1
in the main repo, so I can't see any need for this in proposed now.
But just to answer your question anyway, YES:-
0.52.2-1ubunti1-18.04.1
also fixes the issue (though now it would likely be more accurate to say it doesn't regress the earlier fix).
As far as I was concerned this bug was already fixed in:-
0.52.1-1ubuntu1
in the main repo, so I can't see any need for this in proposed now.
But just to answer your question anyway, YES:-
0.52.2- 1ubunti1- 18.04.1
also fixes the issue (though now it would likely be more accurate to say it doesn't regress the earlier fix).