Just a note that the issue I had (which was primarily a firefox problem) was solved in the most recent build of 5.2.