Category: Web Developing
No full backwards compatibility for you.
As Mozilla Foundation announced the availability of original WebGL (which was based on OpenGL ES 2.0) back in 2011 and then a 1.0.2 update two years later, the development has shifted to WebGL 2 (2013) and now it looks like all companies involved are ready to share some of the progress they have made in the last year or so.
So what exactly does the WebGL 2 have to offer? According to the recently revealed preview, the new graphics library is now based on the OpenGL ES 3.0 API and aims to raise many restrictions that were present in WebGL 1 (such as ability to use more render textures at the same time), developer controlled access to antialiasing, multiple render targets and other goodies.
In a newly published post, the IE Team has revealed the steps they took to modernize its rendering engine (aka split it from the original Trident).
That‘s why Spartan is said to be more compatible than IE has ever been, especially due to a new web approach. Instead of analyzing the top 9000 sites that are responsible for around 88% of all web traffic (like Microsoft did in the past), they actually got to the root cause of compatibility issues and looked for patterns of trillions of urls instead.
Recently, Microsoft has announced a couple new things, first of all, their Pointer Events model has now been accepted by W3C and became a recommended standard, which means that other browser vendors should be implementing it in the near future, hopefully.
In addition to that, there have been changes in the new rendering engine that is set to power Spartan. Due to the double tap issue (where a browser must pause for 300ms to see if there will be another one (assuming users want to zoom)), there comes a delay. While there are many workarounds (even for IE10), they are not ideal.
And boy did we have to wait.
Back in 1999, the IETF and W3C have finalized the HTTP/1.1 protocol and now, 16 years later, it looks like the IETF HTTP Working Group has finally announced the work on HTTP/2 is now complete and it’s on the way to be published as a standard.
Why is HTTP/2 such a big deal? Well, as you might expect from 16 years of progress, it does bring faster page load times, longer lived connections, ability to deliver tons of requests at the same time thanks to the multiplexing feature, which means that the rest of the page load won’t be blocked by some of the heavier items.
Some time ago, we reported that Microsoft was looking for a various user feedback, specially related to the user interface. Well, after collecting and listening the community, the software giant has revealed a newly redesigned F12 developer tools for Internet Explorer.
The main focus of a new design was to optimize the vertical real estate and eliminate the confusion, they claim that for this very reason tools icons were also removed and replaced with text.
And this is how it looks like:
Say hello to the Stack Overflow.
Now here’s a pretty interesting and unexpected decision from the Microsoft itself. In an effort to really please and understand web developers (as well as move everything into one place), the software giant has announced a new migration initiative, which means that from now on, all discussions related to IE development will be moved from MSDN forums to Stack Overflow.
Will bring few new features for web developers.
If you’ve been following status.modern.ie then this won’t exactly be new for you, otherwise, take note.
According to the recent change, the software giant has started working on three new features:
- Responsive Images (image srcset), which will take the advantage of the high resolution screens;
- New input controls for picking dates (all using HTML5 standards): day, week and month;
- A support for MAIN element, which is used to identify the main content of your app or document.
If you are a web developer, listen up as Microsoft is currently looking for the feedback on their new Internet Explorer Developer Tools.
So far, the team has come up with three different layout ideas and this is where your comments and suggestions come into the picture.
Take a look:
BrowserStack, a paid service with over 25,000 customers (including eBay, Adobe and other giants) that allows you to test your web sites on more than 700 different web browser configurations, has been compromised.
The customers has since received the following email:
And it’s pretty useless.
Recently, Microsoft has announced a new and free tool that aims to help web developers to test their code on Internet Explorer, especially those running Mac OS X, iOS or Android.
While it might sound cool on the first sight, there is one problem: it allows you to test the latest version of Internet Explorer on the Windows 10 Technical Preview, which means that pretty much no one is using this browser right now and it’s useless since developers need access to older builds like IE8 and IE9.