HTML/CSS/browser seems a stretch to me. That is view/other bit of view/bit that displays the view
HTML is definitely the Model.
HTML is purely intended to describe (model) the structure of a document. It does not determine HOW the document looks. It only describes the document's contents and structure.
just describes a headline and a paragraph of text. It doesn't say the header should be large or bold, or that the paragraph should have a space above or below it.
CSS is definitely the View.
It has knowledge of the HTML (model) it is presenting and provides details of how it should be presented. The same HTML model can be presented in completely different ways by two different CSS views.
Browser could be viewed as the Controller.
Not a great fit, since the browser typically responds to the user clicking links by requesting a new model from the server, rather passing messages onto the View. But it does fit with the "the link between a user and the system"
The point of patterns like this is to aid understanding. "A software metaphor is more like a searchlight than a road map" as Steve McConnell says.
I find it useful and illuminating to think of the interaction of HTML/CSS/Browser as an example of MVC. So the metaphor works for me.