I have a website built with MediaWiki CMS which I host on a CentOS based Apache "shared server environment" (SiteGround).
This website contains a ContactPage contact form in which the subject field is hardcoded to the form wrapper via PHP;
This is odd, because all other fields aren't hardcoded like this and are actually optional and injected into the wrapper from the form's default template which I pasted into the main customization file of the CMS (
By the way, All of these optional fields are HTMLForm template-engine fields.
If someone wants to remove the subject field from backend whatever reason, it would be a logistical pain, because, for example, after every automatic upgrade, it will have to be removed again, probably manually, from ContactPage extension relevant PHP source code (unlike all other fields which are optional from the very stable file
I want to remove the aforementioned subject field and the only very stable ways I have with the current architecture of MediaWiki, are CSS and JS;
But this is problematic because a user can easily turn off both (most users won't do that, but still).
For now, I have removed the subject field with CSS only but I contemplate to add an "insurance" removal with JS as well to prevent end users that turned off CSS but forgot to turn off JS from whatever reason (say, random cognitive bias) from using that subject field.
Considering IS literature, is it a plausible move to have such "JS insurance" for CSS removals and if not, what will be a better way?