Anne van Kesteren wrote:
Maybe the draft already says something about this, but I couldn't find
it. I think it would be good if there was a way in the IDL to say what
an object stringifies to. The Window object becomes [object Window]
and Location stringifies to its href attribute value.
On Dec 30, 2007 7:19 PM, Cameron McCormack [EMAIL PROTECTED] wrote:
You can however use Object.prototype.toString.call() to ensure you are
getting Object's version of toString(), and not some overridden version:
Object.prototype.toString.call([object Window])
[object String]
On
Anne van Kesteren:
Maybe the draft already says something about this, but I couldn't find it.
I think it would be good if there was a way in the IDL to say what an
object stringifies to. The Window object becomes [object Window] and
Location stringifies to its href attribute value. The
On Dec 30, 2007 5:49 PM, Cameron McCormack [EMAIL PROTECTED] wrote:
Anne van Kesteren:
Maybe the draft already says something about this, but I couldn't find it.
I think it would be good if there was a way in the IDL to say what an
object stringifies to. The Window object becomes [object
Hi Garrett.
Garrett Smith:
Checking an object's toString return value to try and determine what
it is is not a reliable way to check what type of object it is:
toString() says nothing about an object's interface, other than the
fact that, if no error is thrown, it supports toString().
For
Maybe the draft already says something about this, but I couldn't find it.
I think it would be good if there was a way in the IDL to say what an
object stringifies to. The Window object becomes [object Window] and
Location stringifies to its href attribute value. The tricky part here is
Jim Ley wrote:
Could you describe the use cases for defining this at all?
Interoperability. Specifying that Window stringifies to [object Window]
is probably unnecessary (and not true in all UAs anyway). But
specifying that, Location stringifies to its .href property is needed
(and is
