<snip>Neredbojias said:Jukka K. Korpela wrote:
but I hardly consider that a good reason to avoid it's usage.
known to directly cause numerous issues (usually perceived as problems)
in IE browsers, and an alternative exists that can achieve the same
without provoking those issues, there is no need to look for any other
reason for avoiding their use.
In practice the absence of any formal specification would be expected to
result in inconsistent implementations, and that is what is seen. For
expression evaluating to a non-empty string value by replacing the
current document's contents with that string (interpreted as HTML),
IceBrowser will not replace the document with such a string.