{"id":3355,"date":"2016-11-17T16:40:52","date_gmt":"2016-11-17T16:40:52","guid":{"rendered":"http:\/\/www.ckl.io\/?p=3355"},"modified":"2022-07-01T17:55:07","modified_gmt":"2022-07-01T17:55:07","slug":"how-to-build-a-browser-pt-1","status":"publish","type":"post","link":"https:\/\/cheesecakelabs.com\/blog\/how-to-build-a-browser-pt-1\/","title":{"rendered":"How to build a web browser\u200a\u2014\u200aPart 1: Specifications"},"content":{"rendered":"
\n
\n

Browsers are a complex piece of software: inside a web browser there are features comparable to a whole operating system. Every time I googled how to make a web browser<\/em>, the answers were quite shallow, usually talking about how to consume some browser engine and make something on top of it. This article aims to walk through the whole process of making a web browser. On part 1, I\u2019m going to talk about specifications.<\/p>\n

<\/p>\n

In my lifetime experience as a developer, I learned that executing the code is usually the easiest part of the software development process. What really takes time and effort is defining how<\/strong> it should work. That\u2019s what organizations such as the W3C<\/strong><\/a> and WHATWG<\/strong><\/a> do.<\/p>\n

The W3C\u200a<\/strong>\u2014\u200aWorld Wide Web Consortium\u200a\u2014\u200ais an international standards organization, which maintains full-time staff for the purpose of working together on the development of standards for the web. Until 2004, the W3C was the main responsible for standardizing the web.<\/p>\n

To this day, most new features required long periods of time for standardization, followed by implementation by many browser vendors, only then followed by developer feedback and iteration. But this workflow is changing\u2026<\/p>\n

In 2004 an organization formed by Mozilla, Apple, and Opera Software named WHATWG\u200a\u2014\u200aWeb Hypertext Application Technology Working Group\u200a\u2014\u200awas born in response to the W3C wanting to pursue XHTML2\u200a\u2014\u200awhich had no interest from browser vendors. Their proposal was to evolve HTML, rather than invest in XML based technologies, this evolution is known today as HTML5.<\/p>\n

WHATWG proposes a different way of thinking specifications, they call it a living standard:<\/p>\n

This means that they are standards that are continuously updated as they receive feedback, either from Web designers, browser vendors, tool vendors, or indeed any other interested party. It also means that new features get added to them over time, at a rate intended to keep the specifications a little ahead of the implementations but not so far ahead that the implementations give up.<\/p><\/blockquote>\n

But not every feature comes from a standardization group. Sometimes, browser vendors implement a feature needed for its own business and never share a specification with the community. This practice is harmful to the health of the open web and forces browser vendors to spend energy on compatibility, rather than innovation.<\/p>\n

If you read this link<\/a>, you\u2019ll see it is a specification document for window.orientation<\/em>, a feature created by Apple that never really got specified anywhere, so Mike Taylor wrote a spec for it<\/a>. Actually, if you take a good look at the previous link, you will see that the whole document is about documenting non-standard features so all browsers can be compatible.<\/p>\n

But as I mentioned before, things are changing, the community is becoming more mature and the process is getting better. Today it is a lot easier to play a part in the web evolution.<\/p>\n

In 2015, W3C launched a new working group called Web Platform Incubator Community Group<\/a> (WICG). The purpose of the WICG is:<\/p>\n