>Do we think this is likely to have a more robust workaround than this in broader terms?
Don't know until I speak to the development team (assuming this fixes the problem). However its likely the long-term official fix will be to upgrade to a later revision.