Does Google Dart JavaScript converter support older browsers? - javascript

Does the Google Dart JavaScript converter support older browsers or is it only supporting modern browsers?

According to technical overview of its official site :
You will be able to run Dart code in several ways:
1.Translate Dart code to JavaScript that can run in any modern browser: Chrome, Safari 5+, and Firefox 4+ (more browser support coming shortly).
2.Execute Dart code directly in a VM on the server side
3.Use Dartboard to write, modify, and execute small Dart programs within any browser window
There is little chance that the Dart -> JavaScript compiler will support older browsers.

It's supported in no browsers currently. However code in dart can be compiled to JavaScript.

Related

Can I test cross-browser javascript via the command line?

Firefox has the JSShell for SpiderMonkey. Do the other major browsers Chrome and Safari have a command-line interface to their javascript engines? If so, this would be a great lightweight way to test javascript to ensure that it runs cross-browser without having to open a full browser.

How to develop web browser plugins instead of NPAPI(Deprecated from most of browsers)?

I want to develop a browser plugin for RTSP streaming on web browser, I read about NPAPI, which can execute native code(C++). But Google Chrome will not support NPAPI in future and no guaranty about Firefox also.
Please somebody can suggest me to "How can I develop plugin which can execute native code(OR any other language) using other framework instead of NPAPI?".
How can I add RTSP Streaming support for web browsers?
I'm afraid you cannot implement universal plugin at the moment. It's possible to write extensions for Chrome and Firefox which support TCP and UDP sockets (Chrome API, Mozilla API ). No such thing for Microsoft Edge or Explorer or Safari as far as I know.
If using different streaming protocol is an option, consider WebRTC. Its support is still not very good, but at least WebRTC is an official standard and has better chances of being adopted.
If you plan to develop an extension for the major browsers (IE, Firefox, Chrome and Safari) then I'd suggest looking into the kango framework. It takes a common code base and converts it into plugins for 3 of the 4 major browsers (for IE you'll have to contact them)

What is the browser support for the "digitalbazaar/forge" lib (native JavaScript TLS implementation)

I'm using the digitalbazaar/forge JS library, but I cannot find anywhere what the browser support is. Does anybody know?
After some digging we found that forge uses window.JSON and Object.create and other more ECMAScript 5 stuff. This means that out of-the-box the lib doesn't work in IE7 and below.
We included two shims: ES5-shim and Json3 and with those in place the code ran without any issues.
I'm not sure of the comments of #bruno (see above) are valid or not for our use case (we're not using TLS itself, but other encryption stuff that is also in the lib), but with respect from it just running this seems to work on all browsers we tested it in (IE6 and up, chrome, firefox, mobile safari, mobile android and opera mini).
What will be worse in the older browsers is the entropy of the PRNG's seed because they do not have a strong native entropy source, which makes the encryption a lot less secure in those browsers.

Changing the JavaScript engine in side a web browser

It is possible to change the JavaScript engine being used inside a Web Browser?
Some additional information:
For testing mobile applications, I would like to be able to emulate the exact JavaScript engine being used by a web browser to find bugs.
If there anyway to change the javascript engine being used in a Browser such as Chrome or would I need to build my own browser?
This is an interesting feature. I'd like to test Safari Javascriptcore engine in Chrome browser instead of V8. Because I noticed that some of my angular code is not rendered correcty on JavascriptCore engine and rendered correctly on other browsers. It'll be in handy when you found some bugs on ios devices and you have no mac device nearby.
UPD
I found browsers where you can change browser engine lunascape and avant. these browsers are triple engine browsers and you can switch between engines.
There are a number of open source browsers. It is theoretically possible to replace the JavaScript engines they use and compile your own executable. Indeed a number of browsers have changed engines during their history.
You'll probably need to make changes to the API to make them compatible though.
There's no way to do this from JavaScript, of course.
Generally, a given browser ships with a single JavaScript engine. There is no need to ship with multiple engines, because if additional features are required of the engine, they'll simply be added to the engine which the browser ships with.
I could potentially see the existence of a modular web browser which requires plugging in a JS engine separate from the main program (which could then result in the user having multiple JS engines on their machine), but I know of no such browser, and thus know of no means by which JS could be used to swap the engine.
I suppose you could implement EMCAScript in JavaScript, but that seems like a tremendous hassle.
In response to the edits to your question: I believe Chrome Dev Tools' mobile emulation will get you what you want instead of what you've asked for.

javascript engine before nitro (in Mobile Safari)

Lots of articles deal with the "new" js engine nitro on iOS.
For developing and comfortable testing for older iOS devices, I would like to install an outdated browser on windows or ubuntu which is using the same js interpreter?
It's so sad that the js interpreter or js engine differs so much, even with parsing scripts.
To find the right WebKit port, I have to know the name of the "old" js engine. Where to find it?
Thanks
In the case of the pastebin example, there is a syntax error because class is a reserved word and can not be written (with strict js settings like on the old ios webkit).
Use .className instead!
To test with different JavaScript engines and browsers I would recommend using the genius Browserstack. It offers emulators for iOS 3.2 to 6.0 for either the iPhone or iPad. With a comprehensive unit testing suite for your app it should be easy to find engine specific errors.

Categories

Resources