Comment 34 for bug 1683761

Revision history for this message
Tessa (unit3) wrote :

Just ran into this. pretty surprised we're still having issues with a bug that was first identified in 2013. Does anyone have workaround suggestions in the mean time?