28 Sep
2011
28 Sep
'11
9:40 a.m.
Fixed: just for fun I tried using Safari instead of Chrome, and it worked fine - this is probably a Chrome bug, not a Galaxy one. -Alex