Ok, that makes more sense than the Ajax explanation, thank you. :-) If the +addcomment URL becomes used only for POST and redirects straight back to the bug report page, that still would not require +addcomment to return a page of its own on GET, but I accept that it's probably easier for the URL to exist with an associated GET page than without. (IIRC another reason for introducing the redirect, besides simplifying the implementation, was to prevent double-posting when reloading the page manually after posting a comment.)
My original concern, which I should have described explicitly, was +addcomment cluttering up browser histories and URL auto-complete menus etc when you try to revisit bug reports. As you alluded to, fixing bug 381561 will address that. Sorry for the annoyance.
Ok, that makes more sense than the Ajax explanation, thank you. :-) If the +addcomment URL becomes used only for POST and redirects straight back to the bug report page, that still would not require +addcomment to return a page of its own on GET, but I accept that it's probably easier for the URL to exist with an associated GET page than without. (IIRC another reason for introducing the redirect, besides simplifying the implementation, was to prevent double-posting when reloading the page manually after posting a comment.)
My original concern, which I should have described explicitly, was +addcomment cluttering up browser histories and URL auto-complete menus etc when you try to revisit bug reports. As you alluded to, fixing bug 381561 will address that. Sorry for the annoyance.