Atitit. Main browser JS engine core market share Attialx Summary vOa9

Atitit. main Browser JS engine core market share Attialx Summary vOa9

1. Browser Kernel 1

2. The main components of the browser are: 2

2.1. Main Component Architecture 2

2.2. WebCore typesetting engine and JavaScriptCore parsing engine,3

2.3. Rendering Engine Basic Process 3

3. Current major browser engine and browser: 4

3.1. Trident (MSHTML):IE 4

3.2. Presto:Opera7 and above 4

3.3. Gecko:Firefox 4

3.4. Khtml ( derived from WebKit):Safari,konqueror,chromium 4

4. Second,JavaScript engine 5

4.1.1,Chakra Chakra,IE9 new JavaScript engine enabled. 5

4.2.2,spidermonkey/tracemonkey/jaegermonkey,ff 5

4.3.3,V8 used in Chrome, Proud tour 3. 5

4.4.4,Nitro applies to Safari 4 and subsequent versions. 5

4.5.5,Linear a/linear b/futhark/carakan,,opera 5

4.6.6,kjs khtml the corresponding JavaScript engine. 5

5. Browser market share and source 5

5.1. Latest market share figures from NET Applications 6

5.2. statistical aspects of StatCounter 6

6. Reference : 6

1. Browser kernel

The most important or core part of the browser is "Rendering Engine", but we are generally used to call it "the browser kernel

The kernel is just a popular saying, the English name is "layout engine", translated is "typesetting engines", also known as the "page Rendering Engine" (the various statements in the following general). It is responsible for obtaining the content of the Web page (HTML, XML, images, etc.), organizing the information (such as adding CSS, etc.), and calculating how the Web page is displayed, and then outputting it to the display or printing

Author :: Old Wow's paw attilax ayron, email:[email protected]

Reprint please indicate source: Http://blog.csdn.net/attilax

2. The main components of the browser include:

1. User interface-includes address bar, back / forward button, bookmark directory, etc., which is what you see in addition to the main window used to display the page you requested

2. Browser engine-interface for querying and manipulating the rendering engine

3. Rendering engine-used to display the requested content, for example, if the request content is HTML, it is responsible for parsing the HTML and css, and to display the parsed results

4. Network-Used to complete network calls, such as HTTP requests, which have platform-independent interfaces that can work on different platforms

5. UI Backend-used to draw basic components such as combo selection boxes and dialogs, with a common interface that is not specific to a platform, and the user interface of the underlying operating system

6. JS Interpreter-Used to explain the execution of js Code

7. Data storage-belongs to the persistence layer, the browser needs to save a variety of data like cookies on the hard disk ,HTML5 defines the Web database technology, This is a lightweight and complete client storage technology

2.1. Main component Architecture

Kernel "Rendering engine" JS engine

Figure 1: Browser main components

It is important to note that, unlike most browsers, Chrome assigns each tab An instance of its render engine, each tab being a separate process.

2.2. WebCoretypesetting engine andJavaScriptCoreparsing engine,

2.3. Basic process of rendering engine

The rendering engine first obtains the content of the requested document over the network, usually in the form of a 8K block.

Here is the basic flow of the rendering engine after it obtains the content:

Parse HTML to build a dom tree -- build a render tree layout render Tree-- drawing the render tree

Figure 2: The basic process of the rendering engine

The rendering engine begins parsing the HTMLand translates the tags into DOM nodes in the content tree . Next, it parses The style information from the external CSS file and style tag. These style information, as well as The visibility directives in HTML, will be used to build another tree --render tree.

The Render tree consists of a number of rectangles that contain attributes such as color and size, which are displayed to the screen in the correct order.

When the Render tree is built, the layout process is performed, which determines the exact coordinates of each node on the screen. The next step is to draw, which is to traverse the render tree and Draw each node using the UI back-end layer.

It is important to note that this process is done incrementally, for a better user experience, the rendering engine will render the content to the screen as early as possible, and will not wait until all the HTML has been resolved before building and layout render Tree. It shows part of the content as part of parsing, and may also be downloading the rest of the content over the network.

3. Current major browser engine and browser:

3.1. Trident (MSHTML):IE3.2. Presto:Opera7and above3.3. Gecko:Firefox3.4. Khtml (derived fromWebKit):Safari,Konqueror, Chromium

Note:WebKitis an open-source browser engine, with the corresponding engine hasGecko(Mozilla Firefoxand other use of the typesetting engine) andTrident(also known asMSHTML,IEusing the typesetting engine). AlsoWebKitalso AppleMac OS Xname of the System engine framework version, primarily forSafari,Dashboard,Mailand some otherMac OS Xprogram. WebKitof the includedWebCoretypesetting engine andJscorethe engine comes fromKDEof thekhtmland theKJS, when apples were comparedGeckoand thekhtml, the latter is still selected, because it has a clear source structure, very fast rendering speed.

Presto:ms speed is fast .

5,Chromium(cross-platform)

In factChromiumis thatWebKit, Wikipedia does notChromiumfromWebKitThis distinction is based entirely on my own evil tastes. I remember seeing a post from Daniel who said,ChromiumputWebKitcode grooming is much more readable, so it may take a day to compile the code, and now it takes only two hours to get it done. I've never done it myself, but I'm a credible one. And that explains why .Geckoand theWebKitcome out so long, third-party compiled, customized versions are not many, but by theChromiumthe derived browser has long mankengmangu.

Common Chromium kernel browsers:Google Chrome,Chromium,SRWare Iron ,Comodo Dragon

4. Second,JavaScriptengine

Opera has always been a very good runner in JavaScript engines, and in general, the latest beta version of PK,opera Basically will win the championship.

4.1.1,ChAkraCheckCaratIE9enable the newJavaScriptengine.

4.2.2,Spidermonkey/tracemonkey/jaegermonkeyFf

SpiderMonkey application in Mozilla Firefox 1.0-3.0,tracemonkey application in Mozilla Firefox 3.5-3.6 version,jaegermonkey application in Mozilla Firefox 4.0 and subsequent versions.

4.3.3,V8applied toChrome, proud to travel3.

4.4.4,Nitroapplied toSafari 4and subsequent versions.

4.5.5,Linear a/linear B/futhark/carakan,, Opera

Linear A applies to opera 4.0-6.1 version,Linear B applies to Opera 7.0~ 9.2 versions, Futhark applied to Opera 9.5-10.2 versions, Carakan applied to Opera 10.5 and subsequent versions.

4.6.6,KJS khtmlcorresponding to theJavaScriptengine. 5. Browser market share andSource

PC Browser Market share::: IE, FF, Chrome are 30%, Safari 6% Mobile browser Safari 50%, Android 20%,opera 10%,chrome 10%

5.1. FromNet ApplicationsThe latest market share figures 5.2. StatCounterof statistical data

6. Reference:

[ Copvin ] about the browser kernel of some small knowledge, plainly choose the browser! . htm

The Global Mainstream browser market share ranking in the year of the month _ browse fan . htm

2013 year 8 month Global browser market share ranking   -  free green software download shared software base cracked green software free download   -  Unified Download Station .htm

year 8 Month domestic master browser market share leaderboard - See engine kengine _ See news network IT information . htm

How does the browser work? (Working principle) -Internet Explorer Chinese website . htm

Atitit. Main browser JS engine core market share Attialx Summary vOa9