Comment 54 for bug 488857

Revision history for this message
In , Dholbert+bmo (dholbert+bmo) wrote :

Thanks, that's great news!

I believe "INVALID" (meaning "not a mozilla bug") is the correct resolution for that. However, it's probably best to verify that it's actually fixed (for Firefox) in a patched GTK version first.

Perhaps you've already done that? If not, we can wait 'til patched GTK versions make it to distros, and resolve this at that point.