When Sir Tim Berners’ Lee first proposed his idea for a hypertext markup language (HTML), his focus was solely on the organisation and linking of textual information. That is to say, how the content looked was not a priority at the time. The first web page consisted solely of text and links. So there were definitely missing features that authors of web pages were asking for.
The web during the 1990s was pretty much like the wild west, and the early browser vendors were a key reason for that. Mosaic was released by NCSA in 1993, and Marc Andreessen, who led that development team, left for Netscape Communications to work on Netscape Navigator, which proved to be a big hit. Microsoft, who was also eyeing a piece of the Dotcom pie, licensed Mosaic and used it as the basis for Internet Explorer.
Both vendors started to compete with one another in terms of features, and it was common to see websites with badges that stated “best viewed in Netscape” or “best viewed in Internet Explorer”, because code for one browser did not work exactly the same way in another.
It wasn’t until December 1996 when the first CSS standards (CSS Level 1) were published as an official W3C recommendation. At the time, it was fairly rudimentary, allowing authors to control their fonts, colours and spacing between elements on their pages. It also introduced some basic concepts like the box model, style inheritance and the cascade, which remain relevant to this day and are key to understanding how things work.
The thing about web technologies is that they are designed to be backwards compatible, which means that the code written back in 1996 will work the same way when viewed today (although the same cannot be said for code written today when viewed in browsers of yesteryears past). Which is why, if you scour the web for resources, it is a good idea to check the date when the content was written. Because the solutions you find will most likely work for the issue you’re facing, but it may not be today’s best practice any longer.
Modern browsers also push out newer and better features (as well as bug fixes) fairly frequently these days, which means that new techniques are being developed much faster than before. This may be a bit of a challenge as some folks find such a pace intimidatingly frantic, but you can also see it as a very good thing. Because you might find that something that seemed impossible (or extremely hard) to implement a couple months ago is now possible with much less code.
During the twentieth anniversary of CSS in 2016, the W3C published a brief history of CSS until 2016. It is quite a fun read and helps paint a picture of how CSS got to where it is today.
Welcome! Unfortunately, you don’t have access to this lesson. To get access, please purchase the course or enroll in Magical Dev School.
Unlock this lesson