Comment 31 for bug 1393505

Revision history for this message
Ivan Berezovskiy (iberezovskiy) wrote :

This issue wasn't fixed for 5.1.2. It was mistake with changing status to "fix released".