There's been a recent-ish (past 2-3 months?) site update which bypasses that problem, though I cannot find dang's comment announcing that.