Comment 5 for bug 1355284

Yeah, this is like the first implementation actually did it but design explicitly requested the "commit to spread". Will revert it back to the original behaviour. However it's probably not as simple as changing one threshold number so can't really promise it to happen for RTM unless this should be treated as a critical issue.

Vesa, can you update the specs then to reflect this when you have some time so we keep the consistency between spec and implementation?