Validate code field to not contain <script> or <style> tags to prevent human mistakes

That's definitely a good feature, but if we're simply searching for the tag via string search, we might run into an issue:
Let's say that I want to add a string within my JS that contains either <script> or <style>, then the Form would block that, even though this might be necessary in some cases. So would we just be searching via trim() followed by str_starts_with() / str_ends_with(), or do you have a better idea?

I guess it would also be easier for us to check for both tags in both cases, as we could then only add this code to the FormBase instead of both forms, and it would not make any notable difference (JavaScript usually doesn't allow <style> at the beginning anyway and vice versa).

Yeah good point, I agree #2 is a good solution and #4 also totally makes sense to me, as this is just a friendly convenience check to safeguard users from a typical stupid mistake :)

Please do it that way (use an array for tags to check) and implement it in the base.

Please also add a simple test to show it works as expected.

Alright! :)

The general functionality is implemented, along with a basic test! Anything to add?

Nice! Just one little correction to clarify this.

Also please add a code comment to explain why we're not simply checking for "contains" here. That's what you'd typically expect, I think.

Thank you @LRWebks - to me this looks good!

Thanks for this.

I seem to be getting "An error occurred while merging. Try again." on all MR. I've commit the old fashion way.

Automatically closed - issue fixed for 2 weeks with no activity.