How Browser Works
Most people use a web browser like use a car, they have no idea what’s going on the hood. They just turn the key and drive it.
The casual web users nothing wrong with that. just get the string and drive it.
For web designers and web developers, however, knowing what’s going on inside the browsers very important to understand How Browser Works. The key infects ensure that your website looks and perform the way you design them to.
It does not help so many browsers and each of them performs task little bit differently to rest.
It is very important for web designers and developers that what is going on behind the web browsers. Each browser has the own way and task of performing.
We start by taking the basics of How Browser Works.
Discussing why different exists, between them and finish by examining the evolving web standards and what is the means when dealing with browsers.
The Basics How Browser Works.
Web browsers use HTTP (HyperText Transfer Protocol) to communicate to server and request for using web contents.
Once the request is page usually HTML document then browser uses internal rendering engine to translate the page and render on screen.
Any additional contents such as images, videos are requested and rendered based on whether the browser support file type or Whether the plugins necessary view the contents or installed.
So if the basics behind the browser the same way the different browsers behave differently. It is important to remember.
Most browsers developed independently of each other because of this multiple rendering engines each with little bit different preferences, intendancies we see on the web.
So, why are browsers different?
- The browser developed independently of each other.
- Multiple rendering engines drive page layout.
As a designer, it is important to understand which render engine uses the various browser and how to differ when we lay the pages and contents.
The DOM (Document Object Model) allows designers and developers to use scripting to control and creating elements within your document.
Over the years the different level of DOM controls has been created. Another browser support is currently released.
Which means the scripts is executed the way you intended in one browser may have slightly different result and another browser.
At this point browser development.
Now for the notices, the differences between browsers are driven by how the render engines work.
These differences often result in pages either look a different browser to the next the layout look nothing like each other depending on browser use.
In this article How Browser works, it is very important to understand about Web browser rendering engines.
The Four Most Common Web Browser Render Engines.
4. Web Kit.
1. Trident is developed by the Microsoft and propriety engine is used in multi. Internet Explorer uses Trident.
2. Presto is developed by Opera and licenses to other devices.
3. Gecko is an open-source rendering engine. Originally developed by Netscape. But release to open source for Mozilla Projects continues development.
4. Web Kit is another open-source rendering engine, which is developed by Apple, Google, Nokia, and others. It powers browsers such as the Apple Safari browser and Google Chrome.
Therefore, web designers should test their pages not just on multiple browsers but multiple versions of some browsers.
The Browser Wars…
In the mid of late 90s, two browsers.
2. Internet Explorer.
Both of them were badly each other for market dominance. Some refer to that time as browser wars. In order to build a better browser with cooler capability.
Each was released with propriety features and not supported by any other browsers. This meant that every new release web designers would have to learn new ways the development of websites to take advantages of these features.
This would often lead to the designers needing to developing multiple versions of pages for different browsers. just picking up the browsers to design for not worry about the rest.
The browser market became crowded. designer and developers face the impossible task which tries to create pages to look everywhere. This created web standards in 1998.
This created web standards projects in 1998 by the group of designers and developers frustrated the current states of browsers development. they began supporting in an organized way the adoption of w3c recommendations.
The w3c began in 1994 and attempted to standardize web protocols and technologies by issuing a series of recommendations for everyone to follow.
Obviously, at this point no one was listening. So web standards projects started referring to recommendations as standards it attempts to convince browser manufacturers to follow them.
They began education and initiative to make sure designers and developers worry that standards and push for them.
They also educated the general public by encouraging the use of browser support the standards now the at the end designing and developing community with the rise of the browser such as Firefox helped other manufacturers realize advantages and supporting web standards. You can learn more about the standards of the project www.webstandards.org.