This issue has been reported and has already had a fix put in place.
We are currently awaiting the fix to be rolled out to our implementation of the forum software.
Updated Mon Mar 27 2017 22:51
The fix for this issue has now been deployed. Issue resolved.