so, back again with an instance of === not always yielding the same result as == when perhaps it should… it just so happens that code i just wrote, given an empty string, yields a different result comparing that string to “” when using the === operator rather than the == operator.

even more strange, my attempt to create a ‘canned’ test case for this fell flat. i was not able to duplicate the behavior except within the application in which i discovered it.

moral of the story? if you know you’re comparing a string to “”, don’t use strict comparison === in order to test for an empty string. use == instead.