Closed Bug 217464 (tcl) Opened 21 years ago Closed 13 years ago

support TCL

Categories

(Core :: General, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: bugzilla, Assigned: colin)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Mozilla should support TCL script language. Reproducible: Always Steps to Reproduce:
Alias: tcl
Severity: normal → enhancement
great, i wish your luck with implmenting it -> assigning to the Reporter
Assignee: general → bugzilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: general → bugzilla
Reporter, any plan on how you should do this ?
I'm not the reporter, but there are a couple of things that might help. One striking example: content/base/src/nsScriptLoader.cpp // If this isn't JavaScript, we don't know how to evaluate. // XXX How and where should we deal with other scripting languages?? if (!isJavaScript) { return FireErrorNotification(NS_ERROR_NOT_AVAILABLE, aElement, aObserver); } Might instead drop through to load the script even if it !isJavaScript, at which point an instance of nsIDOMHTMLScriptElement for the tcl script might be created, and evaluated, by the (one would have thought simple, but possibly not) expedient of letting nsHTMLScriptEventHandler::Invoke invoke the script. Are there reasons why this wouldn't work fairly simply?
Colin, you want to take this? I'll file the blocking bug to get the multi-script-language infrastructure designed and implemented. /be
Depends on: dom-agnostic
Product: Browser → Seamonkey
Assignee: bugzilla → nobody
Product: Mozilla Application Suite → Core
QA Contact: bugzilla → general
I'll take it, now most of the work's been done :)
Assignee: nobody → colin
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.