User:Eleanorg/annotation/How Web Browsers Work: Difference between revisions
(Created page with " ==notes== ===the parts of a browser=== * UI ::* search bar etc * Browser engine ::* * Beneath user interface, the browser's jobs are distributed between different parts. Of pa...") |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
==notes== | ==notes== | ||
Line 5: | Line 4: | ||
* UI | * UI | ||
::* search bar etc | ::* search bar etc | ||
* | * BROWSER ENGINE | ||
::* | ::* links UI to rendering engine | ||
* | * RENDERING ENGINE | ||
::* Renders content by parsing HTML, constructing DOM tree and adding CSS to 'paint' each element in correct position | |||
::* Firefox's rendering engine is 'Gecko'; Chrome & Safari use Webkit, another open source rendering engine. | |||
::* Rendering engines try to speed up final display by painting initial content before all has rendered. | |||
::* Parsing HTML is more difficult than XML because of its 'soft' syntax | |||
*Networking | |||
::* Gets the data with HTTP requests etc | |||
* Data Persistence | |||
::* Stores cookies |
Latest revision as of 17:30, 19 October 2012
notes
the parts of a browser
- UI
- search bar etc
- BROWSER ENGINE
- links UI to rendering engine
- RENDERING ENGINE
- Renders content by parsing HTML, constructing DOM tree and adding CSS to 'paint' each element in correct position
- Firefox's rendering engine is 'Gecko'; Chrome & Safari use Webkit, another open source rendering engine.
- Rendering engines try to speed up final display by painting initial content before all has rendered.
- Parsing HTML is more difficult than XML because of its 'soft' syntax
- Networking
- Gets the data with HTTP requests etc
- Data Persistence
- Stores cookies