Next

Summary

There is a bug in the current Canary branch, wherein a user reports that they cannot change mature content selector in their settings. The save button, for them, does not highlight and will not save.

Steps to reproduce

(How one can reproduce the issue - this is very important)

Platform information

Os = Linux mint 64 Chromium Version 71.0.3578.98 (Official Build) Built on Ubuntu , running on LinuxMint 19 (64-bit)

What is the current bug behavior?

User cannot change the value of mature content

What is the expected correct behavior?

User should be able to select whether or not they want mature content to be shown by default.

Relevant logs and/or screenshots

https://www.minds.com/newsfeed/945414871000760320

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

/label T - Bug ~"S - Triage:new"

added S - Triage (Unable to Replicate) T - Bug (Triage) labels

added P - Platform label

changed the description

Failed to replicate on Manjaro, running Linux 4.19 in Chromium.

@eiennohi Do you have a Linux system that can test this?

@benhayward.ben

I started with the mature content box checked, and could not turn it off.

In both normal mode, and in the Canary environments, while I was able to clear the check box, upon refresh it reverted to the filled position.

etag

Thanks for the report @luculent , plates full at the moment but this is high priority so I'll try get it into next sprint.

changed milestone to %sprint: Boisterous Buffalo

assigned to @benhayward.ben

changed milestone to %sprint: Clever Chipmunk

added 1 - High T - Bug labels and removed S - Triage (Unable to Replicate) T - Bug (Triage) labels

added S - Backlog label

changed weight to 5

Sorry to bother you @luculent . I want to fix this but cannot reproduce. Could you please try one more time to ensure that its still happening, and hasn't been stealth patched. If it does I think I'll have to VM mint. It's driving me crazy!

Well this is on Debian. Dont Bill use Debian...ask him to give it a try.

I gotta be honest though...I cant see a OS making a difference.

added S - InProgress label and removed S - Backlog label

Yeah, nor can I. I'm just trying to boil down the assumptions I'm making, and that there is no difference between OS's is one of the only ones that comes to mind.

Does this issue persist regardless of what platform your on? I guess if it is it's indicative of a problem with your (and other users) accounts. What that could be though is utterly perplexing.

https://gitlab.com/minds/front/tree/master/src/app/modules/settings/general is the component in question. I'll give it another go over later to make sure everything is fine on the front but it looks like it should work fine.

Do any errors crop up in the networking tab of your dev tools?

Believe it of not, I dont get any console errors at all, under any heading.

added S - Follow Up label and removed S - InProgress label

changed the description

@benhayward.ben Please update on the status here

@luculent Are you still experiencing this bug? I was never able to replicate.