User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040617 Firefox/0.9 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040617 Firefox/0.9 If developers want to respond to comments, currently they have to rate their own project, which is not quite in the best interest of him because it affects the overall rating of his project. Reproducible: Always Steps to Reproduce:

The Rating does not have an asterisk marking it as required. And if you don't pick one, and click the button, all the fields are wiped out. I guess that's a different bug.

If you read the asterisk's content, it says any field with an asterisk is /not required./

I agree that developers need a way to respond to comments and not affect the rating. The Rating field does not have an asterisk indicating that it is required. All other fields have asterisks meaning those are optional. Perhaps this can be done when developers get accounts and can manage their extensions?

humm, there's no practical reason to have a "no rating" comment reply function visable from the general site UI, only from the Developer Login section. So, how should this work? to keep end-users from commenting w/o rating and yet allow developers to respond to comments without turning it into the Mozillazine Forums? heh. This relates to Bug 247409, and Bug 247144.

Looking at some of the comment pages, I'd say there's a very practical reason to give a "no comments" option- namely, some users have install problems, and never get to try the extension in question... but they still rate it. The way things stand right now, a lot of people appear to be using the "user ratings" for help- but why should they be able to rate an extension they've never tried? So, why not make at least one of the two fields (comments/ratings) required, and allow a post as long as one has been filled in (even if the other is blank)? That doesn't even need a UI, then, just a short explanation in an error page if both fields are left blank. Ideally this option would be available to everyone for the reasons stated.

The comments/ratings system is not a forum. Requests for help really should be just ignored there. Giving the authors the ability to null rate and reply is beneficial for the users though, so in it goes. There's no way to know if somebody has or hasn't tried an extension. Granting people the right to comment w/o rating it isn't supported by that. (I could say i've used a product on amazon where I really haven't too.)

Bulk Moving Developer Control Panel bugs to new component. (Filter: massdevcpspam)

Mass-resolving bugs that have been fixed on trunk.

Sorry for the bugspam, reopening bugs wrongly marked as resolved.