On May 15, 2009, at 10:34 AM, Allen Wirfs-Brock wrote:

Note that the host object exceptions in the Es5 spec. permits, but do not require that hosts take liberties with the ES specified object semantics. In particular, there is no reason that a browser cannot implement DOM objects as "native objects" rather than "host objects".

This is what Gecko has done forever, likewise KHTML -> WebKit, AFAIK.

The only "host objects" in Mozilla code have been some LiveConnect (Java <-> JS bridge) ones, but those are being replaced by "native objects" too.


Nor, from an ES specification perspective, there is no particular reason that the ES binding of WebIDL should permit use of host object semantics (which pretty means unspecified) rather than native object semantics. However, those responsible for maintaining and incrementally evolving existing implementations probably would have a different take on this matter.



Anyone working on IE care to comment here, or in a w3c public list? If the latter, a folllowup giving a link to the thread here would be appreciated.

/be

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to