Closed
Bug 1131597
Opened 10 years ago
Closed 10 years ago
Report link reappears in Reviews page
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P4)
Tracking
(Not tracked)
VERIFIED
FIXED
2015-03-03
People
(Reporter: vvalentina, Assigned: kngo)
References
Details
Steps to reproduce:
1. Load MP-stage homepage https://marketplace.allizom.org
2. Open Reviews page for any app (i.e. https://marketplace.allizom.org/app/stay-fit/ratings)
3. Click “Report” link for any review
4. Leave app page
5. Go back to app Reviews page from where you reported the review at step 3
Expected results:
The “Report” link is not displayed in app Reviews page under the reported comment.
Actual results:
The “Report” link is displayed in app Reviews page. If user tries to re-report the review, the message “Sorry there was an issue flagging the review. Please try again later” appears. The “Report” link is no longer displayed after page refresh.
Notes/Issues:
Verified on FF38 (Win 7). Issue is also reproducing on FF OS 2.0 (Flame)
Screencast for this issue http://screencast.com/t/GyAqbsDxXBWe
Updated•10 years ago
|
Priority: -- → P2
Comment 1•10 years ago
|
||
The presence of the regression keyword implies that this did not happen before the desktop ui refresh. Can you confirm that, Valentina? I cannot find any code that would support that.
Flags: needinfo?(valentina.peleskei)
Reporter | ||
Comment 2•10 years ago
|
||
I did not find a screencast with the report section, before desktop UI refresh...sow is hard to demonstrate that this is a regression. I just recall not seeing that (comment #0) before. You may delete the regression keyword if you think is not proper to be there.
Flags: needinfo?(valentina.peleskei)
Comment 3•10 years ago
|
||
If it's not a regression, it probably doesn't belong on this tracker and is likely lower priority than a P3. ni?ddurst for re-triage.
Flags: needinfo?(ddurst)
Keywords: regression
Comment 4•10 years ago
|
||
I'm unclear on when this regression would have happened. ValentinaP, was this working previously (say, a few weeks ago) and recently changed? Or was this just recently noticed?
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → kngo
Priority: P2 → P4
Target Milestone: 2015-02-10 → 2015-02-24
Assignee | ||
Comment 5•10 years ago
|
||
I don't think this is a regression, but it is a valid bug.
Currently, we have an odd behavior where ALL anonymous users can only report a given review once, since we do a user=XXX filter for has_flagged. If one anon user flags a review, and another anon user tries to flag it, a "You have already flagged this review" error will arise, which is weird since they're anon.
And it's impossible to keep track of which anon user already flagged a review. And it'd weird to restrict non-anonymous users that developers can't flag and users can only flag a review once, and to not restrict anonymous users.
So talking to Krupa, we decided to only allow logged-in users to flag reviews, and prompt anon users to log in to flag.
Flags: needinfo?(ddurst)
Comment 6•10 years ago
|
||
Are we sure we want to disallow anonymous flagging ? It is fairly common to let visitors report comments on websites, without forcing them to have an account to do that. I'm concerned that we'd miss useful feedback about abusive/hateful/illegal content if we do this.
For the record, I had noticed this particular bug back when converting the API from Tastypie to DRF and decided to let the behaviour because of this concern. IMHO we could make the message let confusing and simply say "This review has already been flagged" for anonymous users.
Assignee | ||
Comment 7•10 years ago
|
||
Hm, I didn't realize that it is probably okay to allow for all anonymous users to flag a review just once. Although my last hour, I may go with just raising a notification.
Assignee | ||
Comment 8•10 years ago
|
||
last hour will have been wasted*
Reporter | ||
Comment 9•10 years ago
|
||
(In reply to David Durst [:ddurst] from comment #4)
> I'm unclear on when this regression would have happened. ValentinaP, was
> this working previously (say, a few weeks ago) and recently changed? Or was
> this just recently noticed?
Related to Report, i recall seeing the link disappear for non-anonymous users.
Assignee | ||
Comment 10•10 years ago
|
||
https://github.com/mozilla/fireplace/pull/1032 for original STR.
Will also hide Report link to an anonymous user if an anonymous user has already flagged it.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 11•10 years ago
|
||
(In reply to Kevin Ngo [:ngoke] from comment #10)
> https://github.com/mozilla/fireplace/pull/1032 for original STR.
>
> Will also hide Report link to an anonymous user if an anonymous user has
> already flagged it.
Verified as fixed on FF38(Win 7).
Postfix screencast http://screencast.com/t/qYFEoanaJYyJ
Closing bug.
Please see https://bugzilla.mozilla.org/show_bug.cgi?id=1135570
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 12•10 years ago
|
||
I've found the same issue, but following different STR (this issue seems to be related to clicking the "Load More" button from Reviews page):
1. Load MP-dev homepage https://marketplace-dev.allizom.org
2. Open Reviews page for any app (i.e. https://marketplace-dev.allizom.org/app/loqui/ratings)
3*. Click "Load more" blue button
3. Click “Report” link for any review that was displayed after step 3*.
4. Leave app page
5. Go back to app Reviews page from where you reported the review at step 3.
Please see the screencast: http://screencast.com/t/tHaPrQJfQ1
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 13•10 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Target Milestone: 2015-02-24 → 2015-03-03
Reporter | ||
Comment 14•10 years ago
|
||
Verified as fixed on FF39(Win 7).
Postfix screencast http://screencast.com/t/lXzrggWcPB
Closing bug.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•