No, the ticket seems to indicate that the issue should be fixed. However there is a chance that it regressed, i.e. got broken again at a later point in time.
To confirm this theory you could download a build for one of the revisions indicated in the ticket (r69760 or r69842) from
https://reactos.org/getbuilds/ and try whether it's fixed for you there. If it is indeed a regression, please file another ticket, referencing the previous one.
To help pinpoint the problem, you could then start from the known-good revision and the known-bad revision (0.4.6 was branched from r75446), and do a binary search to find out when it stopped working.
Thanks.