For some users of an application I built using ARCGIS JSAPI version 4.12, no graphics appear on maps. The issue does not seem to be browser specific (some users with identical browser versions experienced the issue, others did not) , but does seem to be new to version 4.12 of the API. Are there known causes of this? Some browser or account-level setting perhaps?
I have attached two screenshots from a computer experiencing the issue - one of ESRI's "Intro to Graphics" tutorial page that should show graphics but doesn't, and the second of the Codepen linked from that page, changed to version 4.11, which does show the intended graphics.
I issue with same problem on my computer: Mozilla, Chrome, Opera;
Map shows correctly, graphics are visible.
Client computer same browsers;
Map not showing graphics but layers are created. I can click where graphic should be and popup shows.
Also official graphics example is not working on client computer:
Official example
Screenshot of the issue
Related
My ruby on rails website does not load on safari 15. It works fine on older versions as well as other browsers. The below is what I see in Safari 15
There is nothing in the console logs or any indication of what the "problem" is. Interestingly this is also an issue for my site if I run it locally on localhost:3000 which leads me to think it's an issue with something in my sites code.
If I disable Javascript the site will then load, what in my Javascript could cause this?
I have a similiar problem with my matured React app. Some users of my web application are using Safari 15 and they report that some fragments of the application are not loaded.
I also got screenshots from them. There is nothing indicated in the console.
But interesstingly all the HTML canvas elements are not rendered. Even the small ones.
Some examples:
Leaflet map in canvas (map tiles somehow not rendered):
A chart in a canvas (chart stays blank):
I mean it is working in every other browser since years and also Safari 14 and Safari on iOs.
Must be something Safari 15 realted.
For me this ended up being an issue with Three.js, I needed to upgrade it's version then the site worked in safari. If you're not using Three.js, then I'd recommend checking the other JavaScript packages you are using.
I developed some kind of a Sound-Shooter in A-Frame.
It has actually 7 images and 13 Soundfiles (some between 3-5 MB) in a-asset.
Since november 2019 in my oculus go browser (also Firefox VR) i get the error "Please request the mobile version of this site, to see it in immersive mode". With inspector everything seems fine.
Are there any limitations?!
Addition: Message is from A-Frame. I also got this message on my mobile switching to desktop version of my html-site
Use A-Frame master and serve your content over HTTPS
Problem is gone without code change on my site (exactly how it came). I don't know if A-Frame or Oculus fixed his libraries.
Message has nothing to do with asset limitations. It's a message from A-Frame concerning rights on the website (DeviceMotion)
I'm currently trying to set up a connection between my web client and my iOS app, but for some reason my iOS client only sees a black box when using Chrome (version 33). I can see the video just fine if I use Firefox (both in my app and when I put the browsers side-by-side, they can see each other).
This doesn't appear to be a documented known issue with the JavaScript SDK, and I can't see any recent discussion about this on the forums (last post was mine).
The iOS sample can be located here (samples/OpenTokHelloWorld) with the browser page in samples/OpenTokHelloWorld/browser_demo.html
I suggest cd'ing into samples/OpenTokHelloWorld and running python -m SimpleHTTPServer, as it can't be run from a file:/// path.
Here is what my iPad sees:
Chrome:
Firefox:
And Chrome/Firefox (respectively), both publishing video from the same camera
Edit: after testing on other machines, it may be something specific to my environment even though none of my extensions run in Incognito and I don't have any custom plugins installed.
It looks like the OpenTok mobile SDKs with the specific webcam I was using has issues. On Android the video stream will display for a brief moment then segfault, and on iOS there will be no video at all.
I have tested this many times and could not reproduce what you are seeing in your chrome.
Without seeing any console errors or iOS logs the best suggestion is to try clearing your cache, or maybe restarting your computer (longshot)
Just like in Chrome Developer Tool, I was wondering if there is any tool/extension/plugin which would allow me to export timeline data in Safari. I tried the nightly build of webkit but it does not have that feature. Seems like this is a Chrome specific functionality.
I have to use Safari because I am testing a webapp on iPhone.
I searched around for any hints but could not get any. As of now I am thinking of two options to get the timeline information:
Build a Safari extension
Get Chrome Dev Tool's timeline code and build my own version of webkit (if that's even possible!)
Any guides/insights would be highly appreciated!
Update 1: I downloaded Webkit and found out that it supports remote iPhone debugging through USB. Probably I can find the code for web inspector for Webkit and use that code to export the timeline data.
Safari's Web inspector does use the WebKit remote debugging protocol.
However, Safari does not use TCP/HTTP as a transport layer, thus
making it incompatible with Chrome. source
Thankfully, someone from Google wrote a proxy allowing to overcome this limitation.
I'm in the process of developing a Mobile version of some websites using the MVC4 *.mobile.cshtml system.
Everything is working great except when I try and view the sites on my HTC 8x. I get an outrageously large viewport, no javascript executing, offline touch regions and all-around incomplete pageload such that it doesn't function at all. I'm trying to diagnose/debug and not having any luck.
Using IE10 locally with a User Agent string for Windows Phone 8 doesn't show the same behavior. Further, using my exact UA string in any browser locally does not replicate the behavior. I've tried the various viewport workarounds posted on the internet and those have had no impact either.
I'm not on a Windows 8 machine, so I can't install the SDK/Emulator, but I suppose I could upgrade if no other options present themselves.
Anyone have any additional ideas as to how to test/diagnose/replicate this? I've been Googling for days and haven't been able to find any significant resource about this sort of thing.
This was a combination issue with Output Caching and the MVC DisplayModes bug.