New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft Edge compat #6915
Comments
No idea... I can't run Microsoft Edge myself... 😔 |
I was able to run three.js on android browser version 2.3.7. Also, why are you spreading the same message among many libraries ? EDIT: sry for the brainfart on the accounts, gmail is somewhat misleading... :P |
@Cy-Bo-Rg though Edge is a (very) strictly standards compliant browser, I am doing personal outreach to library authors to check compat and see if there are any issues I can help with or escalate. Thankfully most libraries Just Work™, but given our fragile, coder humanity, we have seen a few bugs here and there (most of which are actually from Edge following the specs closer than others - I know, that's pretty mind blowing to hear from an MS browser). I felt personally reaching out to each library would be maximally helpful to the community, as it gives lib authors a direct line in triaging and assessing what we hope will be a delightful change from IE :) (Note: I just joined MS after running the Developer Ecosystem at Mozilla for 5 years, so I understand and sympathize with any frustration you have over IE and the past) |
I would really appreciate if Microsoft Edge adopted the open formats OGG and WebM. |
I haven't tried Edge yet. As far as I know, things mostly work in IE11, and have been working for the past few versions. My experience is limited though (e.g. no experience with post-processing effects). Here are a few issues specific to IE I am aware of - nothing critical. #6349 Function.name. (Solved by Polyfill) - I assume that one will be in Edge. |
Just got Edge on my (cheap Lenovo z50 with AMD A10 cpu and Radeon R6 gpu) laptop. Experience is better than IE11 so far. WebGL (at least Three.js) performance is still a lot less than chrome (30fps in chrome 7fps in Edge). I noticed one strange visual effect in Edge. I have a "winter" zone with mirror reflection (based on ocean demo) frozen lakes. On rotation the reflected objects kind of "streak" until I stop and the renderer can catch up. Also if I close the browser with my app open, the browser goes non-responsive for a while then finally exits. You can see for yourself at http://www.titansoftime.com. |
There are some important distinctions in terms of supported extensions, the most important I find is the CubeMap LOD extension: https://www.khronos.org/registry/webgl/extensions/EXT_shader_texture_lod/ The other issue is that transparent PNGs (32bit RGBA) are loaded by IE in such a way that their color depth is greatly reduced. https://clara.io/view/42c32462-a1d7-4fb3-ad8e-1aefe39924ed/webgl Please note that I am using the PNG as an RGBM texture, thus I need to preserve the full bit depth of RGB even for small values of M (e.g. Alpha). What it looks like in Edge (yikes!): What it looks like in Chrome: What it looks like in Firefox: |
@bhouston I will get this into the hands of the Edge dev team. |
@mrdoob, there are free VMs for testing Edge. |
MSEdge and Window10 is 5GB... Downloading... 😶 |
Another options is remoteIE, but it's kind of slow for webgl stuff. |
Hey there Threesians,
I am working on assessing, cataloging, and triaging library compat with Microsoft Edge. Do you know the version compat range for Three in Edge? Are all versions fully operable in Edge? Also, do you have any bugs that block features or compat I can help with or escalate?
The text was updated successfully, but these errors were encountered: