Comment 7 for bug 1318029

Thanks Josh! I do think it was fixed with some of the added content changes for 2.7, but, since those were new enhancements, the bug continues to occur in 2.6. Since 2.5 is no longer supported, we probably can't worry about backporting a fix there now.