Comment 4 for bug 2039648

This bug was moved off the 3.2 milestone because 3.2 is now EOL. Moving forward, at the time of writing we will be doing 3.3.x releases for a while, until 3.4 comes out.

We can consider this bug for 3.3.x. There is a work around though and we have a lot of bugs to consider, so we'll need to make a prioritisation call as to if this bug can be accommodated.