Comment 44 for bug 659280

Even if not everyone applauds it, bug 713950 was fixed as suggested a few weeks ago. As a side effect, the problem description of this bug is currently not correct, and it's unclear to me if it's motivated to still keep this bug open.

Of course, as long as the issues mentioned in the above comments have not been properly addressed, I'm not opposed to keep discussing them in a bug. Just wondering if there possibly are better bug reports for the purpose. If not, I would suggest that the summary and description of this bug are changed to reflect the current problem(s).