Comment 2 for bug 1496409

Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

James,

No, I am not seeing this issue on > 3.5 series any longer. I think
it's safe to assume this issue has been fixed there.