W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2005

[whatwg] ECMAScript extensions in Web Applications

From: Krzysztof Maczynski <chris___m@hotmail.com>
Date: Sat, 15 Oct 2005 16:18:29 +0200
Message-ID: <BAY17-DAV6FA7EE46E3A0F631AE0159E7C0@phx.gbl>
>From http://www.whatwg.org/specs/web-apps/current-work/:

"In the ECMAScript binding itself, however, the handleEvent() method of the interface is not directly accessible on Function objects. Such functions must be called in the global scope."

Why is that? Only to declare current browsers compliant? (The name window is enough an offense to accessibility for historical reasons.) Reflection mechanisms (abound in ECMAScript) will be of limited use, especially in multi-language programming. Special treatments will need to be hardwired into development tools (debuggers, inspectors, wizards, code editing assistants, metadata handlers). Disobeying design principles sooner or later tends to turn out to be short-sightedness.

If you really want at this price to legitimate current implementations, at least make this hideous practice optional, not mandatory. And deprecated from the start.

Best regards,

Received on Saturday, 15 October 2005 07:18:29 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:43 UTC