Mozilla has been doing a lot of work on their rendering pipeline, and I suspect that the behavior you're seeing is fallout from that. Since it's already fixed, it's just a matter of waiting for the changes to propagate to the release builds. They're on a 6-week cycle, so assuming those fixes get promoted in the next release, you should see them land relatively soon.