Chrome sees the DOM for what it is, not for what it was

Setting the stage

I was browsing through a website for a job application when my curiosity regarding how the website could have been rendered kicked in.

I noticed a name “Callens” in the job application as the person to contact in case I had any further doubts.

I first checked the page source on Chrome. Was unable to find the name in the page source. The page source is the original HTML file sent by the server to our Chrome browser. This suggests to me that the name Callens was not in the original HTML file sent over by the server. Rather, when I clicked the job advertisement to view more details about it, Javascript might have inserted the job description along with the name “Callens” here. This is a classic example of client side rendering. The server was not involved in adding the name “Callens” to the Document Object Model (DOM) at all.

Now, I tried to save this page using Chrome’s “Save page as” feature. To my complete surprise,