Travis Leithead:
I can think of some interesting use cases for implementing [[call]]
on an interface object... I'd prefer to leave it unspecified at best.
OK.
I agree with Hixie on the point of specifying the behavior of typeof,
and to me typeof HTMLDocument == 'function' makes sense, since
On Mar 19, 2008, at 12:08 AM, Maciej Stachowiak wrote:
ECMA-262 actually allows typeof to return anything at all for host
objects (which all of the DOM binding objects are). So it would not
be an ECMA-262 violation, technically, for an uncallable object to
give typeof == 'function',
On Wed, 19 Mar 2008, Cameron McCormack wrote:
So really the only options are:
* don’t say anything about [[Call]], and thus allow typeof to return
'object' or 'function',
I don't believe that's a real option.
* mandate that [[Call]] is not implemented, and thus require typeof
Maciej Stachowiak:
ECMA-262 actually allows typeof to return anything at all for host
objects (which all of the DOM binding objects are).
Of course you’re correct, I forgot about that.
So it would not be an ECMA-262 violation, technically, for an
uncallable object to give typeof ==
Ian Hickson:
Those are two possible options. There's also a third option: allow
interfaces to define [[Call]] the same way you allow them to define
[[Construct]], thus making this vary on a per-interface basis.
All right. So since as Maciej points out some interface objects do need
to be
On 18/03/2008, Travis Leithead [EMAIL PROTECTED] wrote:
Since this spec is presumably creating a language binding for JavaScript,
(and assuming interface objects are Functions, as seen by Opera), then why
does:
var div = new HTMLDivElement();
produce a script error?
Only having heard
Jonas Sicking wrote:
Anne van Kesteren wrote:
On Tue, 19 Feb 2008 11:31:50 +0100, Jonas Sicking [EMAIL PROTECTED]
wrote:
I do sort of think that it's a pity to disallow a selectors
implementation in a browser from implementing additional selectors on
top of the ones in the CSS
Boris Zbarsky wrote:
Is there a reason to have identical interfaces called DocumentSelector
and ElementSelector that are identical? Would it not make sense to just
define a NodeSelector or something and require Document and Element
nodes to implement it? The confromance requirement could
Boris Zbarsky wrote:
I've been thinking about this some more, and the requirement that the
caller be able to tell apart the NSResolver returning a String and some
other object that has a toString() method is actually a bit of a pain.
For example, in Gecko a C++ caller into this API would just
Boris Zbarsky wrote:
Is there a reason why querySelector(All) is not supported on
DocumentFragment nodes? It seems to me that such support could be
useful... It's already supported on disconnected subtrees rooted by an
Element, as far as I can tell, so it doesn't seem like the
Boris Zbarsky wrote:
Is there a reason to have identical interfaces called DocumentSelector
and ElementSelector that are identical? Would it not make sense to just
define a NodeSelector or something and require Document and Element
nodes to implement it? The confromance
On Wed, Mar 19, 2008 at 9:12 AM, Jonas Sicking [EMAIL PROTECTED] wrote:
Travis Leithead wrote:
Since this spec is presumably creating a language binding for JavaScript,
(and assuming interface objects are Functions, as seen by Opera), then why
does:
var div = new
All:
As per our conversation a few weeks ago. Attched please find some DRAFTS
of how to collect Metadata for our test suite and a DRAFT of an
overview document.
Please make comments as you see fit. Please bear in mind that this
documents are very subject to change and should be by no means
Hi, WebAPI fans-
The minutes for the DOM3 Events telcon on 19 March 2008 can be found here:
http://www.w3.org/2008/03/19-webapi-minutes.html
Or as text below:
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Web API WG Teleconference
Hi, Web API fans-
We will be holding a telcon next Wednesday to review and discuss the
keyboard aspects of the DOM3 Events spec, specifically the Keyboard
events and key identifiers [1] and Text events types [2]. There is good
work in these, but they are not yet complete. I would
15 matches
Mail list logo
