SC.Widget('id_of_widget').play(); doesn't seem to work on iOS (v6 in pod touch). I've been trying to get it to work on my own site, (http://www.fromabrokenheart.com/119) but couldn't. All is fine in other browsers I have tried on windows.
I then tried the html widget playground (http://w.soundcloud.com/player/api_playground.html) and that is not working on my ipod touch either. The play button above the console does not work.
In the console on the playground, I get continual "loadedProgress": null.... errors... see attached screenshot... I could not see the full error there...
any thoughts?
Nick
Related
My basic static React Redux TypeScript app works locally on Windows, and then it also works when I deploy to GitHub Pages for every device I've tested except iPhone 6 iOS 12.0.1 (where it is a blank white screen).
I've researched many articles, such as:
React/redux app renders blank screen on Safari
React/Node Uncaught SyntaxError: Unexpected token <
Why deployed react app on gh-pages is showing blank page on different browsers while showing correctly on my browser?
https://stackoverflow.com/a/57027870/470749
https://community.netlify.com/t/react-application-builds-deploys-into-a-blank-page/2571
https://github.com/facebook/create-react-app/blob/061d1e46fcd4766d38b45499c3d29cfaa2b7d0af/packages/react-scripts/template/README.md#github-pages
https://caniuse.com/#feat=es6
Most of them try to solve the case where all devices show a white page. But that's not my scenario.
Others talk about how older browsers need polyfills, but I've already added try/catch blocks around my use of fetch.
I've also tried changing to "homepage": "." in package.json, but again, I don't think that's related to the issue because most browsers already work, so I know that the assets are being accessed.
Any ideas?
Finally I remembered that I could use the free http://xip.io/ service to browse from my iPhone to the "local" React server hosted on my Windows machine.
That way, I could see error messages that wouldn't be visible on production (at GitHub Pages).
I discovered that the error was "ReferenceError: Can't find variable: IntersectionObserver".
So the solution would be to use a polyfill.
See helpful links:
https://stackoverflow.com/a/55767479/470749
https://stackoverflow.com/a/59368511/470749
https://github.com/mhartington/lazy-load-image/issues/1#issuecomment-372384646
https://webkit.org/blog/8582/intersectionobserver-in-webkit/
https://caniuse.com/#feat=intersectionobserver
"IntersectionObserver API is supported on iOS Safari since 12.2." That explains why it worked on other iPhones but not mine.
https://github.com/tensorflow/tfjs/issues/1384#issue-421174127
TensorFlow.js version
1.0.0
Browser version
Google Chrome: Version 73.0.3683.75 (Official Build) (64-bit)
Describe the problem or feature request
I followed the steps from Google Codelab: https://codelabs.developers.google.com/codelabs/tensorflowjs-teachablemachine-codelab/index.html#0
The given example works fine, but when I made some changes to the example for my Blog with multiple images, it gives this error:
As you can see, when I click on the first image, it works fine. Loads the model, does classification, displays the results. As I click on a second image, it gives these errors. This seems to be happening on this Windows Laptop [Dell Inspiron, Windows 10] with this Version of Chrome only as I am also testing the same thing on a MacBook Pro with the exact same version of Chrome without any errors.
Code to reproduce the bug/link to feature request
You can check my Blog here [https://anujdutt9.github.io/TFjs-ImageClassifier.html] and look for errors in the console. Also, you can find the complete code for this here [https://github.com/anujdutt9/anujdutt9.github.io/blob/master/TFjs-ImageClassifier.html].
This issue was resolved by using an updated version of TensorFlow.js. Take a look at the code with the update here: https://github.com/anujdutt9/anujdutt9.github.io/blob/master/TFjs-ImageClassifier.html
Hej
When testing one of the modal windows on https://angular-ui.github.io/bootstrap/#/modal my chrome browser freezes for about 50 seconds after I close the modal. For this time I can not do anything in that specific browser tab. I can not even scroll.
The console output does not show any errors.
I implemented the component modal in my own web app and the same happens.
Does anybody know about that issue?
Version of angular: 1.5.0
Version of angular-ui-bootstrap: 2.4.0
Version og Google Chrome: 55.0.2883.95 (64-bit)
OS: macOS Sierra 10.12.2
Btw: In Safari everything works fine.
Recently I came across with a similar issue. and Then figure out it's because of the CSS Display:block Attribute check try making it in to null on your modal div. this will take you in to the modal and out from it smoothly.
Hope this will help you some how.
I'm using Angular on my site, but I've been having reports on it often not working. Often users have to try different browsers/devices to get it to work. On my computer it works fine on Chrome, Opera and Firefox, latest versions. I've had reports of the page not working for visitors when using Firefox (version 31.6.0) and Safari though.
I have a smartphone of brand Öwn (Chilean or Peruvian I think), and the angular code does not work on this phone. I've tried using Chrome and the Öwn browser (some browser of their own). I have expandable content powered by jQuery, and that works fine, so it's definitely only Angular the page has problems with.
I tried removing all dependencies (using ngAnimate and ui.bootstrap for datepicker, and ngDialog), but still doesn't work on my phone.
I'm sorry I don't have more details. This is the page where the problems happen:
https://www.easterisland.travel/tours/
Does anyone have a clue? Thank you!
The problem in the end was in the code of an Angular function. When declaring a new object, I hadn't applied a value to one of the variables. This:
var tourObj = {groupId: groupId, pricePP: pricePP, savingsPP};
should have been this:
var tourObj = {groupId: groupId, pricePP: pricePP, savingsPP: savingsPP};
It was tricky since some browsers accepted it (Chrome and later Firefox) but many didn't. To locate the problem I checked error console of Safari Mac, and all it said was that angular.min.js.map and angular-animate.min.js.map were missing. .map files are for showing debug messages with minified code. Once the .map files had been added (find .map files for angular here, clicking folder for your angular version), the error console showed me exact location of the error.
I have an qx v2.0.1 app working off the local file system and it runs fine in Firefox v14, but in Chrome v18 it gives me this error:
Uncaught Error: The theme to use is not available: edd.theme.Theme
qx.Class.define.members.initializeMeta.js:108
qx.Class.define.members.mainAbstractGui.js:82
qx.Class.define.members.baseObject.js:141
qx.Class.define.members.mainApplication.js:38
qx.Class.define.statics.readyBaseInit.js:77
qx.Class.define.members.dispatchEventDirect.js:134
wrappedFunctionInterface.js:451
qx.Class.define.members.dispatchEventManager.js:873
qx.Class.define.statics.fireEventRegistration.js:310
qx.Class.define.members.__fireReadyApplication.js:188
qx.Class.define.statics.onScriptLoadedApplication.js:106
qx.$$loader.signalStartupedd.js:159
qx.$$loader.initUrisedd.js:195
I thought I've come across this before and a ./generate.py distclean fixed it, but not this time. Someone else had a similar bug that was fixed:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=1463
Any ideas?
This question is too tricky, and probably involves things like looking at verbose generator output and your job configs, so it is not really suitable for a Q&A site. I suggest you open up a bug for it at the qooxdoo project.
Interestingly enough, after a computer reboot it started working in chrome again. So the chrome clear browser cache/history everything since the beginning of time must not catch everything. So now it's working again...odd.