On May 21, 2012, at 4:19 AM, Wes Garland wrote: > This thread brings up an interesting question: > Once we have modules, should we have a place other than ECMA-262 to define > standard host-environment libraries that ship with browsers?
Like the DOM?? ;-) We are already working on one example, the Internationalization API. But note that is being developed so that it is not specifically browser dependent. So far, there have only been a few issues that have come up that potentially relate to browser integration and those have generally been bypassed as being out of scope. Using that as an example, I can propose a couple criteria for which libraries might be within the prevue of TC39: * it requires extensions to the base language syntax or semantics or core libraries * it is of general utility in a variety of hosting environment, not just the browser * it must be "baked in" to an implementation * it raises significant interoperability issues that are solvable at the specification level * TC39 has the appropriate domain expertise or experts are willing to join and participate in TC39 Also, we want to discourage libraries from depending upon "host object" semantic extensions permitted by ES <=5.1. If a library thinks it needs them it probably needs to have T39 involved. Every library wouldn't match each criteria, but the more the better. Allen _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
