Https is transport integrity. If you download malware, https ensures that it gets to you in one piece. (or anything else you wish to receive) What I meant is

Https is transport integrity. If you download malware, https ensures that it gets to you in one piece. (or anything else you wish to receive) What I meant is that once the content has been delivered to the browser, it will not be displayed unless the integrity of the payload is ensured. A dumb example, because I am not creative tonight. You download a book, Neuromancer by Gibson. The book is stored in an encrypted zip file. The zip file is delivered to you via https. You can't read the book unless you know what the key is. If the zip file has been altered post download, it probably will not open even if you know the correct key. On the web one could argue that if such a mechanism was possible, then it would "protect" people. Let's say Bob is doing his weekly online banking and crypto investing. Bob isn't that good with computers. Malware is everywhere, maybe someone has been able to sneak an extension into Bobs Chrome browser and it modified the content so he transfers his crypto to the extension authors account. If the page was unable to be displayed less its integrity was ensured this would save Bob money. Yes I agree that as the web exist today with an unholy smear of html,css, JavaScript, Pictures, links, cookies etc it would be difficult to do. But we can go beyond what we have now. Imagine if someone has slid a nefarious extension into your browser. it can change anything it wants as things sit now. T