Professional Documents
Culture Documents
First, it’s important to understand how a web browser actually works.When a user visits a
website, the browser sends a request for that page to the server, which sends back a whole bunch
of code in return. In order to display the page correctly, the browser has to know how to read and
interpret that code correctly. This is done by something called a rendering engine.The guidelines
for how a particular piece of code should appear to the user is laid out in detailed specifications,
but how each rendering engine actually goes about interpreting the code is different from engine
to engine. This individualized approach can lead to a website looking different in different
browsers.
Disadvantages
Brittle When browser-vendors created new vocabularies, those vocabularies would make
pages 'break' in competitors' browsers. The W3C's efforts to call a halt to new vocabulary
development mostly froze a set of compromises in place.
Underpowered HTML never really did all the tasks developers wanted it to do. Part structure,
part formatting, this creature of convenience wasn't always convenient.
Server-Centric Because Web browsers provided only a very limited set of capabilities for
processing information in the browser client, servers had an enormous amount of work to do.