I'm using speakjs in my webapp and in chrome and firefox it runs without errors, however on attempt to run the speakjs client in safari I receive the following error:
ReferenceError: Can't find variable: Float64Array
I have attempted searching through the js and replacing Float64Array with Float32Array but to no avail.
How can i go about solving this?
Update Safari to the current version. It implements Float64Array.
I don't have an answer for getting Safari 5.x to work with code that uses it. I am currently struggling with that.
Update: Luckily for me my usecase of Float64Array came from the emscripten box2d build. Simply replacing Float64Array with Float32Array did the trick for me for Safari 5! It made it work on older versions of Firefox (I tested version 10) also.
Related
I've been anxiously awaiting the release of Safari 11 on OS-X and iOS 11. Now that they're finally here, I can use Safari to record audio data from the microphone -- except that the long-promised support doesn't actually work.
I'm running macOS Sierra 10.12.6 with Safari Version 11.0 (12604.1.38.1.7). The following demos all fail with errors:
https://www.webrtc-experiment.com/RecordRTC/ -- Unhandled Promise Rejection: [object DOMError]
https://www.webrtc-experiment.com/msr/audio-recorder.html -- media error -- TypeError: undefined is not a constructor (evaluating new Recorder(mediaStream))
https://webrtc.github.io/samples/src/content/peerconnection/webaudio-input/ -- Failed to get access to local media. Error: ReferenceError
I've been able to code my own demos that work in FF/Chrome/Edge but capture only "empty" audio in Safari 11 while displaying no errors.
Can anyone out there confirm this behavior? First off, I need to know if I'm alone in seeing WebRTC completely broken in Safari 11.
Next up is Safari 11 in iOS. This is much harder for me to test. It seems like all the demos above are also broken on iOS. Safari 11 on iOS Simulator in XCode doesn't even seem to support WebRTC at all whereas actual Safari 11 on iOS reports to the browser that it's supported but, like desktop, it doesn't actually work.
Does anyone know what in the world is going on? As far as I can tell, the Safari 11 that was just pushed out to iOS 11 and Sierra not only doesn't support audio recording, but MUCH worse, passes the getUserMedia feature detection code implying audio can be captured (but it never actually works).
I'm curious if upgrading to High Sierra fixes anything but I don't want to try because even if it works there, I need access to a broken state to try and come up with some way to work around the busted feature detection.
I need to get a handle on this but it's proving difficult because the only documentation online says that "Safari 11 supports the audio portions of WebRTC" which I cannot replicate anywhere on either my phone or desktop.
Any help or confirmation would be appreciated.
The webaudio-input demo fails due to the lack of an unprefixed AudioContext. Try if
window.AudioContext = window.AudioContext || window.webkitAudioContext;
fixes things
Also see this issue about some hacks required to make things work.
I am trying to build a simple AngularJS application using an old Chrome (version 2010).
Then I am facing various problems with routing. Basically Chrome becomes unstable, even crashes often.
I suspect that my old Chrome is not compatible with the specific AngularJS I am using (v1.3.8).
Where can I find such information? I mean the version of Chrome needed by AugularJS of specific version?
I searched AngularJS document, but didn't get a clue.
Edited:
Quoted from link https://code.angularjs.org/1.3.8/docs/misc/faq:
We run our extensive test suite against the following browsers: Safari, Chrome, Firefox, Opera 15, IE9 and mobile browsers (Android, Chrome Mobile, iOS Safari). See Internet Explorer Compatibility for more details in supporting legacy IE browsers.
I think these details above are a little vague as a reference. I understand the recommended practice is upgrading Chrome to the latest. As "Derek 朕會功夫" commented, my environment is restricted to some extent. One of the restrictions is, it is not feasible to upgrade Chrome.
That is why I want to find out the exact Chrome version supported by AngularJS. People may come up with similar concerns with other browsers like Firefox. Right?
thanks!
Answer To PSL: I am not using bangrang.
BTW, "add a comment" link doesn't work for me , so I have to comment here :(
As far as I can tell, you require Chrome 13 (MDN) from 2011 in order to support the functions tested in the Angular source found here, such as File and Blob.
Recently I have been considering using Polymer elements in a project I am working on. However, I am unable to see any elements being rendered in the new beta version of safari for OS X 10.10 Yosemite. I completely understand that Yosemite and Safari are currently in the DP phase, but I am curious as to why the new verison of Safari has broken compatibility with Polymer elements (I can confirm Polymer elements work in Mavericks version of Safari).
I was able to open the developer console and spot an error. I am unable to reach the exact error at this time, but I know the error was at patches-mdv.js at line 57, claiming a Read Only error.
I just tested the Polymer Project website on my iPhone with iOS8, having the same results.
Does anyone have an idea on what I could do to fix this issue temporarily until the Polymer-Project team fixes it?
One apparent problem is that the Safari beta has at least one low-level property accessor (specifially HTMLBaseElement.prototype.href) that is misconfigured from the standard.
So, cursory investigation implies this is a bug in Safari, not Polymer.
Does Firefox fully support HTML5 APIs? I have seen in some other questions (I cannot remember where) that BlobBuilder is not supported in Firefox.
In addition, when I try to use BlobBuilder object in JavaScript, I am getting an error says "BlobBuilder is not defined". I am using Firefox 4.0b7 version for HTML5 based development.
Given that searching MDC for BlobBuilder turned up no results, and that on the latest daily build (Firefox 4b13), running BlobBuilder resulted in a reference error, I believe that this API will not be implemented in Firefox 4 when it comes out of beta (which will be very soon, given that no blockers remain)
http://www.caniuse.com/#cats=HTML5,JS_API
Looks like recent versions of FireFox support almost everything in HTML5 (including API's)
If I am using many js files in my project and get JavaScript errors in IE 6 or 7's status bar, then how can I trace, find and solve those errors in Firefox? I know how to trace a problem in IE with visual studio but can we identify area of problem using Firefox?
For Internet Explorer use the Developement Tools of Internet Explorer 8 (press F12).
Internet Explorer 8 supports the Internet Explorer 7 engine.
However Firebug is easier to use and much more powerful!
use firebug.
I would recommend using Firebug (http://getfirebug.com/). It's a plugin for Firefox and does a great job of reporting errors to you. It also has a javascript debugger and a great DOM viewer - both of which are very helpful in fixing scripting bugs.
Web Developer for FF [https://addons.mozilla.org/en-US/firefox/addon/60] can be helpful if you are interested in looking at warnings and other code errors that don't necessarily trigger errors - at least in FF.
Cleaning up your code using this or other tools like JSLint [http://www.jslint.com/] will make your code more manageable in the long run. But in the end, each browser's JavaScript engine just behaves differently, and errors in one specific browser will ultimately have to be debugged in its own environment.
One such error that can you scratching your head even between versions of IE is the misformed object below:
var myObj = {
1 : "val1",
2 : "val2",
}
alert(myObj);
In IE8 and all other major browsers the extra comma after the last entry is overlooked. IE6 and 7 will throw an error. But the Web Developer plugin for FF shows the following warning:
Warning: trailing comma is not legal in ECMA-262 object initializers
Source File: http://localhost/test.html
Line: 10
Source Code:
}