@Niharika I noticed you removed Anti-Harassment-Team, is that because your team is no longer maintaining this tool? :)

If you point me to the codebase I can probably submit a pull myself

In T227715#5733281, @jrbs wrote:

@Niharika I noticed you removed Anti-Harassment-Team, is that because your team is no longer maintaining this tool? :)

If you point me to the codebase I can probably submit a pull myself

No, no. We'll maintain this tool. I took it off because it was marked as low priority so I'd rather keep this task only on the Wikimedia-Takedown-Tools board and not over-populate the already overburdened Anti-Harassment-Team board until we're ready to take it on.
I believe the code is at https://github.com/wikimedia/takedown-tools
If you want us to work on it, let me know and I'll pull it in.

I had a look at this and I'm not sure I can do this (I'm not familiar enough with the language). In particular, I see this line in create.js:

<button type="button" disabled={disabled} style={ { zIndex: 0 } } className={cpButtonClass} onClick={() => this.updateField( 'type', 'cp' )}>Child Protection</button>

I can just switch disabled={disabled} to disabled=true, which would in theory work but I wonder if there's a more efficient / flexible way to do this?

In T227715#5770817, @jrbs wrote:

I had a look at this and I'm not sure I can do this (I'm not familiar enough with the language). In particular, I see this line in create.js:

<button type="button" disabled={disabled} style={ { zIndex: 0 } } className={cpButtonClass} onClick={() => this.updateField( 'type', 'cp' )}>Child Protection</button>

I can just switch disabled={disabled} to disabled=true, which would in theory work but I wonder if there's a more efficient / flexible way to do this?

That should unconditionally disable the button, indeed

In T227715#5770819, @Reedy wrote:

That should unconditionally disable the button, indeed

cool. I guess I'm just not familiar with the curly braces and where it's pulling the settings from. If there's a settings file in the repo I should modify instead it might make sense to do that instead...

{disabled} is basically a variable. but it's defined on the fly depending on state/status, not in a settings file

		let disabled = this.props.takedown.status === 'saving',
			dmcaButtonClass = 'btn btn-secondary',
			cpButtonClass = 'btn btn-secondary',
			takedownTypeForm,
			metaDataField;

The other option is you can just remove the button completely (and then at a later date someone can remove the code that it uses)