The "if" expression tests for truthiness, while the double-equal tests for type-independent equivalency. A string is always truthy, as others here have pointed out. If the double-equal were testing both of its operands for truthiness and then comparing the results, then you'd get the outcome you were intuitively assuming, i.e. ("0" == true) === true. As Doug Crockford says in his excellent JavaScript: the Good Parts, "the rules by which [== coerces the types of its operands] are complicated and unmemorable.... The lack of transitivity is alarming." It suffices to say that one of the operands is type-coerced to match the other, and that "0" ends up being interpreted as a numeric zero, which is in turn equivalent to false when coerced to boolean (or false is equivalent to zero when coerced to a number).

这都是因为ECMA规格…"0" == false，因为这里指定的规则http://ecma262-5.com/ELS5_HTML.htm#Section_11.9.3…if('0')的结果为true，因为这里指定的规则http://ecma262-5.com/ELS5_HTML.htm#Section_12.5

在PHP中，字符串“0”是假的(false-when-used-in-boolean-context)。在JavaScript中，所有非空字符串都是真值。

技巧是==针对布尔值并不在布尔上下文中求值，它转换为数字，在字符串的情况下是通过解析为十进制来完成的。所以你得到0而不是truthiness boolean true。

这是一个非常糟糕的语言设计，这也是我们尽量不使用不幸的==操作符的原因之一。请使用===代替。

这是因为JavaScript在布尔上下文和代码中使用类型强制

if ("0") 

将在布尔上下文中被强制为true。

在Javascript中还有其他的真值，在布尔上下文中会被强制为真，因此执行if块:-

if (true)
if ({})
if ([])
if (42)
if ("0")
if ("false")
if (new Date())
if (-42)
if (12n)
if (3.14)
if (-3.14)
if (Infinity)
if (-Infinity)

// I usually do this:

x = "0" ;

if (!!+x) console.log('I am true');
else      console.log('I am false');

// Essentially converting string to integer and then boolean.

显示问题的表格:

和= =

这个故事的寓意使用===

表生成credit: https://github.com/dorey/JavaScript-Equality-Table