Browsers Will Freeze its User-Agent Strings

The User-Agent HTTP header was introduced in 1993 by the first web browser. The string was as simple as Mosaic/0.9. It could be used for good purposes. Web servers can serve slightly different content to browsers that might implement new standards differently. Sadly, Google is abusing its dominant position by blocking or malfunctioning its services for competitive browsers. Therefore, a new mechanism for declaring the technical aspects of a user’s device is emerging. Read more ›

EdgeHTML rendering engine is discontinued

The EdgeHTML rendering engine, a fork of Trident, which is a fork of Spyglass Mosaic, which is a fork of Mosaic, will be replaced by the Blink rendering engine, a fork of WebKit, which is a fork of KHTML, which is a fork of Khtmlw. The existence of standards and minority implementations does not prevent the emergence of monoculture. Microsoft knows this effect very well. Contributing to Chromium rather than developing a proprietary component of Windows will allow Microsoft to deliver its proposed standards to the majority of developers instead of a minority. Read more ›

What drives the development of Microsoft Edge?

Microsoft is very open about developing its web browser. Currently, the team dedicated to its development is significantly larger than it was in the previous few years. By removing the old code for compatibility with Stone Age websites and leaving it to its fate in IE, the implementation of new standards in the modern browser is significantly faster than it was in the past. All that remains is to tell Microsoft what it should focus on in its development. Read more ›

Edge will also be available for iOS and Android

The Microsoft Edge web browser will expand from Windows to other operating systems – Apple’s iOS and Google’s Android. Since the end of Windows Mobile development, Edge didn't make sense even on a PC, because it lacked synchronization of bookmarks, favorites and passwords with the mobile phone. Microsoft is therefore extending user support to other mobile operating systems. Edge is purely a user interface thing, not an EdgeHTML and DirectX port. Read more ›

New Features in Microsoft Edge 15.15063 for Developers

Windows 10 Creators Update contains a stable release of EdgeHTML 15. It allows developers to process payments via Microsoft Wallet. Content Security Policy Level 2 supports several new directives. The Brotli compression format is now supported and is more effective than gzip. The TCP connection can be reopened faster. The latest version also introduces an experimental implementation of WebAssembly. Read more ›

Google pointed out that Microsoft Edge is more secure than Chrome on Windows

Microsoft released security update number 3200970 today. It patches a vulnerability that Google discovered and published before it was fixed. However, this marketing move backfired on Google, as it turned out that Microsoft Edge users on Windows 10.0.14393 are better off than Google Chrome users. Read more ›

New Features in Microsoft Edge 14.14393 for Developers

The Windows 10 Anniversary Update contains a stable release of EdgeHTML 14. It supports loading browser extensions from the Store. Edge supports a new HTML, JavaScript, and CSS-based extension model. Existing Chrome extensions can be easily migrated because this new model is Chrome-compatible. For more details, see supported APIs. Read more ›

What’s new in EdgeHTML 13.10586 for developers

The new build of Windows 10 with the number 10586.3 and the designation 1511, Threshold 2, or Fall Update also includes a new rendering engine for Microsoft Edge. Among the significant changes, the support for ams.js, WebRTC and the ever-improving ES6 support stand out. Support for the handy attribute a[download] or CSS value initial has also been added. The new Windows Runtime finally allows the use of Drag & Drop. From HTML, you can now use the element template, meter, picture, or the w unit in the srcset attribute. Read more ›

What is Microsoft Edge like after 3 months since launch

Sometime a year ago, Microsoft started working on a new browser and a quarter of a year ago it began to be available to the public. At the same time, it enjoyed great interest from journalists. What is Edge actually like? What makes it so different from other browsers? What can we expect from it and what can we forget? Why is it still not popular and what does Microsoft intend to do about it? What caused Edge to fail to meet the expectations of so many users? I tried to find answers to these questions. Read more ›

Interesting facts about Microsoft Edge – the new browser for Windows 10

Windows 10 includes a new web browser. It’s called Edge and it’s built for the modern web, whose content is much closer to full-fledged applications than to a large library of static, text-filled pages. Its creators are open to new standards and suggestions from web developers. It is to bring new features every month. The same version is compiled for both x86 and x86-64 processors and ARM, so the same browser runs on both desktop computers and phones. Read more ›

Development of Web Components for Microsoft Edge has begun

Web Components is an effort to introduce custom controls into HTML5. A control that is isolated, having its own source code and user interface was a common thing in Delphi or Windows Forms (UserControl class). In the world of web technologies, however, everything is still glued into one big confusing whole. We have one object, such as a search box, in three different places. Somewhere there is HTML, somewhere there is CSS and somewhere there is JavaScript. The new HTML element Template can encapsulate everything. Read more ›

Project Spartan, Part 5 – Windows API for Web Applications

With the advent of Windows 10, it will be possible to host application content on its own server. Even so, such a web application will have access to the Windows Runtime, an interface that was previously intended exclusively for native applications. The web app will be right next to the native app in the Store. At the same time, it will be possible to develop and deploy it in the same way as a website. The Windows Runtime will be accessed from JavaScript. Web applications in Windows will be absolutely equivalent to native applications. Read more ›