Earlier quoted context omitted.
Microsoft had a competing proposal to WebRTC called CU-RTC-Web which, as far as I understand it, proposed to get rid of the Session Description Protocol (which is text-based and thus difficult to parse/edit) and provide lower-level APIs instead (details here: http://www.tokbox.com/blog/what-the-cu-rtc-web-vs-webrtc-deb... ). I've just started reading up on ObjectRTC but I believe it plans to offer an API to replace S…
> which is text-based and thus difficult to parse/edit That's not what I normally conclude when I think "text-based."
Status IE – IE's feature status and plans
51–60 of 88 posts
Re: Status IE – IE's feature status and plans
#52Chrome's dashboard: http://www.chromestatus.com
Thanks for the link. I always found it hard to know what is happening in new versions of chrome and which feature became available when. This is exactly what I needed - Thanks! Also found chrome dashboard easier to use than IE dashboard but that's understandable as this is new effort. And, if anyone from IE team is here, how about some consistency with developer tools with other browsers as well. The web developer UI…
Re: Status IE – IE's feature status and plans
#53Re: Status IE – IE's feature status and plans
#54Re: Status IE – IE's feature status and plans
#55Note that this site lists WebGL as "IE11+". That's false. IE11 has a flavor of webgl that's experimental (prefixed or not) that's reported as version WebGL 0.92 (this is basically an invalid specification conformant string, it's either 1.0 or something not done). Huge gaps and bugs remain in Microsofts WebGL implementation which make it nearly impossible to use except for specific select usecases that Microsoft optim…
We shipped an update to the IE11 WebGL implementation to developers today as part of Windows 8.1 Update. We will roll this out to all IE11 users through Windows Update starting next week. There will be further updates to our WebGL implementation in the summer. If there are specific use cases that you're interested in support for, please let us know what they are so that we can prioritise the order of our implementati…
Another measure that's also very useful is to run the webgl performance regression test suite every day to see if performance got worse or better with the changes.
Unfortunately there isn't a comprehensive GLSL syntax test suite, but GLSL has been much of a sore point in IE where some syntax that's valid GLSL would work except in IE (such as uniforms separated by a comma).
I've submitted some tickets to IE (and added more conformance tests to cover them) for some of the gaps (gl.SAMPLES, gl.STENCIL_BITS, gl.SUBPIXEL_BITS).
A thing that's also a sore point is IEs lack of support for very common extensions such as OES_texture_float_linear, WEBGL_compressed_texture_s3tc, WEBGL_depth_texture, OES_standard_derivatives, OES_vertex_array_object, ANGLE_instanced_arrays, OES_element_index_uint, WEBGL_lose_context. You can get an overview of the state of support on http://webglstats.com/
A note on floating point texture extensions. If you implement one extension (for instance OES_texture_float) you should really implement the companion extensions as well for texture_float_linear and color_buffer_float. Only the triplet of extensions provides comprehensive overview of support.
Personally I'd like to see these run in IE of course: http://codeflow.org/entries/2013/feb/15/soft-shadow-mapping/ http://codeflow.org/entries/2013/feb/04/high-performance-js-... http://codeflow.org/webgl/deferred-irradiance-volumes/www/ http://codeflow.org/webgl/trails/www/ http://codeflow.org/webgl/barycentric-wireframe/www/ http://codeflow.org/webgl/ssao/
I think the demos above are fairly good usecases for gaps that you might have, because they exercise a lot of functionality, they're not bound to some specific framework (like three.js) but they are WebGL conformant.
Re: Status IE – IE's feature status and plans
#56Re: Status IE – IE's feature status and plans
#57Chrome's dashboard: http://www.chromestatus.com
The best I can think of is googling for release notes for current beta/aurora [1][2] for "coming soon" but it lacks long term things.
[1] https://www.mozilla.org/en-US/firefox/29.0beta/releasenotes/
[2] https://www.mozilla.org/en-US/firefox/30.0a2/auroranotes/
Re: Status IE – IE's feature status and plans
#58http://kangax.github.io/es5-compat-table/es6/
Shows future versions of Firefox and Chrome but not yet IE.
Re: Status IE – IE's feature status and plans
#59I think that gaining consensus in developers' mindset goes through forcing updates like Chrome and Firefox do; don't care if it's monthly, quarterly or yearly, but users shouldn't even realize that an update was pushed to their machine. This model has shown that it works for browsers, and not only that, it has also proven to be the best model. Is there any actual actionable plan on this?
Adding new features in IE15 is fine and good, but won't buy a dime in developer consensus, when we still waste time supporting 5-years-old IE browsers at any given time.
Re: Status IE – IE's feature status and plans
#60I would like to know from the IE team if there's a specific plan to fix the browser update issue, that is the fact that IE is by far the slower browser when it comes to user upgrades. It's exciting to see features in IE1x+, but we all know that those will be a tiny fraction of users for a long time. I think that gaining consensus in developers' mindset goes through forcing updates like Chrome and Firefox do; don't ca…