Web Browsers - 2020

1. Major Browers
   1. Internet Explorer 8
   2. Firefox 3.6
   3. Chrome 4
   4. Safari 4
   5. Opera 10.53




2. Comparison of web browsers



3. Layout Engines/Rendering Engines
   
   Layout Engine is software that takes mark-up content such as HTML, XML, and image files and formatting information such as CSS or XSL and displays the formatted content on the screen. A layout engine is typically used for web browsers, email clients, or other applications that require the displaying or editing of web contents. Comparison of Layout Engines
   
   
   1. Gecko: Mozilla Firefox
      Gecko is the layout engine built by the Mozilla project and used in all Mozilla branded browsers and software.
      One of the nice features of Gecko is that it is cross-platform by design, so it runs on several different OS, including Windows, Linux, and Mac OSX.
      
   
   
   2. Trident: Internet Explorer
      Trident is the layout engine that Internet Explorer has used since version 4.0, and it sometimes referred to as MSHTML. AOL Explorer and Netscape use it as well.
      
   
   
   3. WebKit: Safari and Chrome
      The WebKit engine provides a set of classes to display web content in windows, and implements browser features such as following links when clicked by the user, managing a back-forward list, and managing a history of pages recently visited.
      WebKit was originally created as a fork of KHTML as the layout engine for Apple's Safari; it is portable to many other computing platforms.
      
   
   
   4. Presto: Opera
      Presto is a layout engine for the Opera web browser developed by Opera Software.
      After several public betas and technical previews, it was released on January 28, 2003 in Opera 7.0 for Windows; it is the browser's current layout engine. Presto is dynamic: the page or parts of it can be re-rendered in response to DOM and script events.
      Presto is available only as a part of Opera browser or related products.
      

      Why is Opera moving to WebKit? Because it has to. - GigaOM Feb 13, 2013
      Opera has confirmed that it's adopting the WebKit rendering engine and the Chromium framework. Why? Apple and Google have so much influence that the mobile web is being written to their specs.

The news that Opera is shutting down the development of its own browser rendering engine and moving to the open source WebKit engine caused quite a stir earlier this week.

With WebKit powering the built-in browsers of Google's Android and Apple's iOS, it's already the de-facto standard engine for mobile and it has the potential to do the same on the desktop. Worldwide, Chrome now holds a considerable lead over Microsoft's Trident-powered Internet Explorer and Mozilla's Gecko for Firefox already. The question is: are we better off because we have competing engines trying to outdo each other, or would we be better off if all the browser vendors just standardized on WebKit?

For more, The Pros And Cons Of A WebKit Monoculture - from Techcrunch Feb 17, 2013

Qt5's WebKit C++ programming: please visit

1. Qt5 Webkit : Web Browser with QtCreator using QWebView Part A
2. Qt5 Webkit : Web Browser with QtCreator using QWebView Part B
3. Video Player with HTML5 QWebView and FFmpeg Converter