When using the Autodesk Viewer in different browsers, sometimes models do not display with textures and instead show black. This has been encountered in Chrome on Ubuntu 16.04, as well as Safari on iOS 10.3.3.
What causes this? If this isn't known, how can we begin to debug this?
We found an undocumented updated to the viewer - version v2.16. We have updated to use this version and the models are now rendering correctly.
Related
I have an angular 2 application in production environment that allows you to choose a profile picture. Recently, performing tests with safari mobile, specifically for IOS 13.3.1 version(older) and IOS 13.4.1(new) version. I noticed that the image is shown rotated depending of safari browser version used (I built a stackblitz for this that you can review):
IOS 13.3.1 version(older)
IOS 13.4.1(new)
When I take images from an iPhone's in portrait mode and upload the image to my app it is shown rotated only for IOS 13.3.1 version(older). However, I examined the EXIF meta-information images from each of my devices and found that both images have the same value in the orientation property:
IOS 13.3.1 version(older)
IOS 13.4.1(new)
My question is. Why does the image display change depending on the IOS version, knowing that in both cases the orientation EXIF is the same value (6)?
This is a subject that worries me since I had already solved this problem by rotating the image depending of EXIF orientation value for its correct display (e.g. exif.js have been created to handle this situation by detecting the exif orientation flag), but this problem now appears again with the new version of IOS. What would be an example of code that I can use to make it sustainable over time? Is there not a consensus among the browsers to manage the orientation of the images?
What is the explanation for this illogical behavior?
Thank you so much!
We also stumbled upon this when our mobile suddenly behaved differently and finally find the root cause of this.
Both WebKit (iOS) and Android (Chrome) have just recently changed the default behavior of the image-orientation CSS propterty. While it was none before, it is now from-image. This means: Before, they ignored the EXIF data of an image by default, while they are now using it to auto-correct the image. Which break our own auto-correction based on the exifreader library.
Here are some relevant links:
https://www.fxsitecompat.dev/en-CA/docs/2020/jpeg-images-are-now-rotated-by-default-according-to-exif-data/
https://bugs.webkit.org/show_bug.cgi?id=89052
Funny enough, also the Slack team seems to have run into this:
https://bugzilla.mozilla.org/show_bug.cgi?id=1634180
Fortunately, the author of the exifreader library (who just some weeks later ran into the same problems) also guided me to a way to detect the behavior. You can find his answer here:
https://github.com/mattiasw/ExifReader/issues/99#issuecomment-640217716
I also noticed that Modernizr has a test for this, so I am actually using a custom modernizr build now to detect the browser behavior.
The webkit browser is rotating the images before you upload them based on the EXIF data then it gets applied again by your app. We were able to confirm this on new (81) version of Chrome and Mobile Safari on 13.4. then the app is rotating them further and it gets twisted.
SPA built with Vue.js that uses Forge Viewer doesn't render simple model in Ios Safari browser (iPhone XR, 13.5.1 ios, ipad). It's not the known issue with big (more than 200 mb) model crashing, the model is slim, over 16 mb. This model is rendered well in PC browsers and in browsers on Andriod devices. The version of Forge Viewer is the latest (7.24), but I also try to use older ones (7.20, 7.12). Does anyone know any solutions to start to show models on Ios devices?
The first error is 'THREE.WebGLRenderer: EXT_color_buffer_float extension not supported.'
Minimal working example on codepen
Just today I found this bug. It shows strips on baselayers. The image below shows how it looks in OpenStreet map and Mapbox. The strips are not there on Firefox.
My Chrome version is 59.0.3071.109 (Official Build) (64-bit).
My Openlayers version is 3.20.1
Is there any fix for it?
The primary reason for this is raster reprojection. If your base layer is in a different projection than your view, OpenLayers will reproject the images of the tile source.
But the particular issue you are seeing was fixed in v4.0.0 (see https://github.com/openlayers/openlayers/pull/6344). So upgrading to a newer version will resolve the problem.
I have an AngularJS (1.58) webapp showing some maps with ui-leaflet.
I have integrated the Leaflet.Heat Plugin, successfully. Also, I have integrated the Leaflet.Draw Plugin successfully.
Problem:
The moment Im using both Plugin, Heat and Draw, my webapp is not showing any maps anymore on microsoft browsers (Microsoft Edge, Internet Explorer 11). I have tried to use different combinations of release versions of these plugins to get it to work on every of the common browers. When I bring the leaflet maps back to working on Microsoft Edge, the Heat Plugin is not anymore working (not only ME, also not Opera, Firefox, GChrome).
Summed up:
The latest versions of ui-leaflet, Leaflet, ui-leaflet-draw and Leaflet.Heat
are working fine together on Google Chrome, Firefox, Opera. But the maps are totally disappearing for Microsoft Edge. Older versions are showing maps again for Microsoft Edge, but the Heat Plugin is not anymore working on any browser.
Question: Is there a working combination of versions of these tools for all these browsers (speaking of Google Chrome, Firefox, Opera, Microsoft Edge) together? If so, which versions are them? If not, are there recommended workarounds? Maybe other plugins, which I can use instead for drawing or showing well-looking heatmaps?
Steps to reproduce:
Download the Leaflet.Heat example. Integrate ui-leaflet-draw as Librarys (e.g. via bower).
Test it with Google Chrome, Firefox, or Opera. Depending on your versions, you gonna either see the working Heatmap but tested with Microsoft Edge you dont see any map OR you dont see any heatmap, and microsoft edge shows u a map (also without heat).
Alright, I was focusing my issue and find a solution.
I replaced ui-leaflet-draw with leaflet.Draw plugin and the combination of all 3 worked for all browsers (as long as I am using the correct versions).
So here they are from my bower.json project file:
"dependencies": {
"angular": "1.5.8",
"angular-simple-logger": "~0.1.7",
"ui-leaflet": "1.0.3",
"Leaflet.heat": "https://github.com/Leaflet/Leaflet.heat/archive/gh-pages.tar.gz",
"angular-material": "~1.1.1",
"leaflet.draw": "*"
},
"resolutions": {
"angular-material": "~1.1.1",
"angular": "1.5.8",
"leaflet": "1.0.3"
}
Update: Leaflet 1.0.3 working too and has better user expierence controls then 0.7.x
Enjoy developing nice maps with Heat layers and Draw controls now working for GChrome, Opera, FireFox, and Microsoft Edge! (havent tested IE 11 cuz of lots of other conflicts with angular-material)
Starting some time around March 13th, I started receiving bug reports from
users that my KML polygons were no longer transparent on Windows XP, and IE8.
I did notice Windows XP updates were applied before issues were first reported to me.
The transparency works fine on any other OS/Browser I have available to test.
(Windows XP with Chrome and Firefox, IE11 on Windows 7, Firefox and Chromium on Ubuntu 10)
Nothing has changed in my generation of the map, or the KML it uses.
I've been able to recreate this with a very simple test:
http://itic.occinc.com/googleMapTest.html
It uses this KML:
http://itic.occinc.com/test.kml
I've tried using different colors in the KML with more and less opacity/transparency.
For now I've disabled the polygon filling in my applications, but I'd like to re-enable that.
Any suggestions are appreciated.
This bug was reported at https://code.google.com/p/gmaps-api-issues/issues/detail?id=6540 and should be resolved