This issue is resolved and working fine on version: Version 184.108.40.206.20180522175053_3940873, hence I am changing the status from on-qa to verified. Thanks for fixing this issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.