Bug 18103
| Summary: | Non-JS scripting languages | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Darryl McAdams <psygnisfive> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Enhancement | ||
| Priority: | P1 | ||
| Version: | 523.x (Safari 3) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
Darryl McAdams
It would be very useful if WebKit (and all other browsers, but especially WebKit) had non-JS scripting language support. Perhaps even something that enables the coder to create language interpreters/translators that can be referenced like
<script type="text/custom:<interpreter-url>">...</script>
What the interpreter would look like I couldn't say; perhaps a parse table + mapping to an underlying set of standard functions implemented in the browser's language of choice, I don't know. But it'd be really useful to be able to have a language other than JS for doing front end work, and being able to specify the language on the fly like you specify can specify other parts of the document (DTD, for example) would be very beneficial. And if the on-the-fly method is chosen, it would make it less work on the developers so they don't have to then decide what languages to implement, etc.
I believe Mozilla is working on something similar, but I don't know how that's going.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Please work with WHATWG on features like this first. Unilaterally adding them to a single engine would be bad for the Web.