Your comment has a more reasonable tone
I think the mis-understanding is that bugs are probably most often reported by developers using jquery to develop web pages
I am not such a person. I do not develop using jquery and I have no interest in doing so. I am just a user whose web experience was affected negatively by this bug
I was surfing the web and the error occurred and the ie9 debugger highlighted that particulr code, so I thought I would let you know.
I want the web to be bug free no matter what technologies are used.
I cannot remember which site it occured on.
You are right and that not **all** functions need to check their arguments.
If function A is called and checks its arguments before passing them on to function B, then B has no need and indeed should not check them again
But some function somewhere should check the argument before trying to access properties on it
The error did occur and the debugger highlighted this code which is calling properties on an object which the function does not know exists, so it seems a reasonable assumption that the debugger is correct
So you have at least one site (not in developement but actually already out in the real world) which is causing this function to fail, and thereby reflecting badly on a library that, as you say, you are giving of your time to maintain and therefore must care about
As a maintainer I assume you know jquery well. In that case I would guess it would take a few seconds for you to create some code which results in this getText function being called with its argument being null or undefined
Checking the argument exists before accessing its properties seems a quick and easy protection against failure. It would probably have been quicker to fix the code than to reply to my comment
As I say, it is not my problem, and I don't care if it gets fixed or not apart from the very general desire that the web provides an error free user experience