User:Eleanorg/annotation/How Web Browsers Work: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
::* Rendering engines try to speed up final display by painting initial content before all has rendered. | ::* 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 | ::* 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