Comment 14 for bug 533566

While this is indeed not a software bug but a design choice, it is so wrong that I'm inclined to think it might constitute a bug in the design guidelines themselves.

There is no exceptional advantage that justifies this change. It seems nothing but whimsical and fails to take into account serious usability issues such as muscle memory and misclicks; more thoroughly outlined in Yokozar's article.

Such a drastic UI change should be backed up by facts that objectively define a clear advantage that outweighs the inevitable user reception obstacles.

On a side note, I think that the "its a choice, not a bug" responses are childish and harmful to the healthy dialogue these report systems are designed to nurture. We all know its not really a bug, but its an issue that demands discussion and dismissing it on such a technicality is seriously immature. Grow up and stop avoiding the issue.