non-typesafe compare with null throws ExpressionException

Description

Having null support enabled, comparing a complex value against null throws an ExpressionException when using the non-typesafe operator ==. Using the typesafe operator === works as there is no attempt to cast the complex value.

 

 

This is an unexpected behavior and casting to String seems to indicate an improper fallback.

I would have expected it to work like Javascript:

This bug is possible related to .

Environment

Status

Assignee

Michael Offner

Reporter

Alexander Kwaschny

Labels

None

Affects versions

Priority

New
Configure