4 ms·
The web browser has very little to do with this problem; it is merely doing what the website has told it to do (or not to do). I run a small forum where clicki
by wvenable 18y ago
The web browser has very little to do with this problem; it is merely doing what the website has told it to do (or not to do).
I run a small forum where clicking back and forth between forms without losing what you've typed is a very important feature. It works exactly the way this author wants in all browsers because the headers are set correctly.
Similarly, I also work on a big web application where clicking the back button and getting stale information is bad. Again, the website sets the proper headers and the information is refreshed (if appropriate) or left alone (if appropriate).
This is not a browser issue. The differences are likely caused by how different browsers implement (or don't implement) the standard.
- ido 18y agoExactly. A lot of so called "browser problems" are actually website problems. And who's the genius that decided accepting malformed html was a good idea? If the first browsers gave an error (with line numbers and explanations) instead of trying to render incorrect html people would just go back and fix it.
- cousin_it 18y agoI've taught a lot of people the basics of HTML. Always started the same: open a text file, type in "Hello World", save as .html, open in browser, see Hello World. Woohoo, instant rush, this stuff isn't so complex after all. Don't want to see this: Error at line 1, DOCTYPE expected
- ihumanable 18y agoYour argument is that you've started teaching a lot of people HTML by showing them something that has nothing to do with HTML, clap clap clap clap clap clap clap...
- cousin_it 18y agoEase of adoption has a lot to do with HTML.
- wvenable 18y agoMost of the enhancements made in HTML over the last few decades would be impossible if browsers didn't render incorrect HTML. Even simple things, like having closed single tags (<br/> vs. <br>) is only possible because old browsers are really forgiving.
- IsaacSchlueter 18y agoBe strict in what you send, and forgiving in what you receive. Browsers are just following this basic networking principle.
- lucumo 18y agoWhich headers are you talking about?
- wvenable 18y agoCache control headers
- ggchappell 18y ago> The web browser has very little to do with this problem; it is merely doing what the website has told it to do (or not to do). I don't agree. It's my browser. It should do what I want it to do, not what the website wants it to do. And what I want it to do is exactly what this guy says.
- bonaldi 18y agoPerhaps the problem lies with what the browser does when no cache control headers are present? I just checked with by loading and then leaving a Guardian.co.uk page, and Safari reloads it from server when you click back. Checked both the page headers and the HTTP headers, and there's no expiry date set anywhere. My preference in this case would be for back to work "properly" unless a site explicitly requests a reload. Doing it that way would solve another back issue that stings me from time to time that the author doesn't mention: forms. I'll have filled out a form, hit submit and hit a network snag for some reason or other. Try to hit back to rescue all that typing, and the browser tries to reload the damn form. Stuck. When I hit back, all I want is to go to the previous page, instantly, precisely as I saw it when I clicked the link to take me away. No reloading, nada.