Looks like the fix for this will be released as part of 3.5.1, at a guess.