fix textbound invalid input

[adityagarg06]

Resolves #6298

Changes:
Added an additional check for invalid input. Also I have written test for the same

• npm run lint passes
• Inline documentation is included / updated
• Unit tests are included / updated

[limzykenneth]

We don't usually handle incorrect parameter types this way as the FES is usually the one to take care of it. In terms of logic it should either do type coersion or return sensible default values, null is probably not useful in this case and can cause a property access error on the user's end.

[micuat]

to me, coercion into string makes sense in case of a number. but then what if the input is an object, for example?

[munusshih]

I think this should be handled in FES. Making an exception for this function might be a workaround for now, but doesn't seem to provide a general solution for this types of problem.

[Qianqianye]

I think this should be handled in FES. Making an exception for this function might be a workaround for now, but doesn't seem to provide a general solution for this types of problem.

Thanks @munusshih. I'm wondering what the GSoC FES contributor and mentors think about this @almchung @nbriz @Ayush23Dash

[Ayush23Dash]

+1 to what @limzykenneth said. Returning a null is not a good solution. Moreover, this might solve the issue temporarily but we need to have a general solution rather than a customised one.

[dhowe]

status ?

[limzykenneth]

@dhowe I'll close this for now as the implemented solution is not necessarily what we needed.