Claims that browsers transform "d.csdfdsaf" -> https://d.csdfdsaf, but they don't. They only transform domains with valid TLDs, unless you manually add the URL scheme.
It is a good one to fix. Thank you!
Readit Newskrasun commented on Show HN: An interactive guide to how browsers work howbrowserswork.com/... · Posted by u/krasun
krasun commented on Show HN: An interactive guide to how browsers work howbrowserswork.com/... · Posted by u/krasun
Not all browsers had or have a DOM, and some didn’t until later versions.
Early browsers without DOMs (with initial release date): WorldWideWeb (Nexus) (Dec 1990), Erwise (Apr 1992), ViolaWWW (May 1992), Lynx (1992), NCSA Mosaic 1.0 (Apr 1993), Netscape 1.0 (Dec 1994), and IE 1.0 (Aug 1995).
Note: Lynx remains a non-DOM browser by design.
AOL 1.0–2.0 (1994–1995) used the AOLPress engine which was static with no programmable objects.
The ability to interact with the DOM began with "Legacy DOM" (Level 0) in Netscape 2.0 (Sept 1995), IE 3.0 (Aug 1996), AOL 3.0 (1996, via integrated IE engine), and Opera 3.0 (1997). Then there was an intermediate phase in 1997 where Netscape 4.0 (document.layers) and IE 4.0 (document.all) each used their own model.
The first universal standard was the W3C DOM Level 1 Recommendation (Oct 1998). Major browsers adopted this slowly: IE 5.0 (Mar 1999) offered partial support, while Konqueror 2.0 (Oct 2000) and Netscape 6.0 (Nov 2000) were the first W3C-compliant engines (KHTML and Gecko).
Safari 1.0 (2003), Firefox 1.0 (2004), and Chrome 1.0 (2008) launched with native standard DOM support from version 1.0.
Currently most major browser engines follow the WHATWG DOM Living Standard to supports real-time feature implementation.
Thank you for the suggestion! Would be writing something like "DOM in the modern browsers" more correct then?
krasun commented on Show HN: An interactive guide to how browsers work howbrowserswork.com/... · Posted by u/krasun
Bit unfortunate that more than half of the page is dedicated to network requests, but almost all work and complexity of the browser is in the parsing and rendering pipeline.
Will cover the rendering engine in more details. I didn't know at what sections to go deeper. So just stopped and published it to gather more feedback.
Thank you!
krasun commented on Show HN: An interactive guide to how browsers work howbrowserswork.com/... · Posted by u/krasun
I like it very much --> bookmarked :-)
The step I am missing is how other resources (images, style sheets, scripts) are being loaded based on the HTML/DOM. I find that crucial for understanding why images sometimes go missing or why pages sometimes appear without styling.
I thought about this, but I tried to keep it simple. Let me figure out how to add these blocks without over-complicating the guide.
Thank you!
krasun commented on Show HN: An interactive guide to how browsers work howbrowserswork.com/... · Posted by u/krasun
krasun commented on Show HN: An interactive guide to how browsers work howbrowserswork.com/... · Posted by u/krasun
Neat, it's like an exciting way to dive into https://browser.engineering without having anything to install.
I'm wondering if examples with Browser/Server could benefit from a small visual, e.g. a desktop/laptop icon on one side and a server on the other.
I am planning to add more sections with more details. But decided first to collect some feedback.
Thank you! It is a good suggestion. Let me think about it.