|
oh my god i am so tired
|
|
By Defect , Section Dev Notes []
Posted on Thu Dec 14, 2000 at 06:23:50 PM PST
|
 |
|
this is just a reminder to me of what i wrote and i need to rewrite it. view the contents below if you feel so inclined.
|
By adding two variables to the get string and having a non-integer value for one of them can allow users to rate comments a fractional value rather than the integers [0..5].
By adding "&rating_[COMMENT #]=[RATING VALUE]&rate=Rate%20All" to the end of a url (as long as it has sid and op set correctly) you can give comment [COMMENT #] whatever rating you want (fractional or otherwise), as long as it is between 0 and 5 (or 1 and 5 if the user is not trusted (i checked this, so there isn't a bug with untrusteds rating comments 0)).
It'd be hard to find a good example to link to because the effects are most noticable when you rate a comment that hasn't been rated before, and once the first person were to click on my example, then no one else would get the same effect. This is not a serious bug, in fact it would've been kind of handy to use occasionally because i sometimes think that a comment deserves something like a 4.5 or a 3.5, but can only vote 3,4, or 5. (also, you're not able to rate your own comments by filling in one of your comment's id's for [COMMENT #], i checked that as well.)
My only suggestion, if you want to see this first hand, is to find a comment that hasn't been rated yet, and add the above two variables to the url (erase any anchor name reference) and just make [COMMENT #] the # of the comment and [RATING] a number like 4.89 or something odd. After the updated page loads, the rating of the comment will be 4.89 (or such) and the drop down will read that you voted 5.
(side note, by adding a correct pid to the url and the two above variables you can rate comments that are nested several levels without actually going to them. not a bug so much as just a pointless hack)
|
|
|
Story Views
|
|
4 Scoop users have viewed this story.
|
|
