K. Peachey wrote:
I believe it's to do with the limited support for JavaScript in the browser, I have already filled a bug [1] about it when I noticed this happening.
Excellent. :) I've also sent a note to Hampton, but I think he's out at a Ruby conference this weekend so might not have a chance to poke it for a few days.
Anyone know if there's an emulator available for that system which we can test with? Otherwise it might end up waiting until we get ahold of a test unit unless someone with one can figure out what's going wrong at the JS level.
-- brion