This is also used as a poor man’s live feed: just use this element to reload the page or frame on a set interval.
Ah, and next you might discover one of my favorite unresolved browser issues:
My fav was Marquee. Could put one inside the other, make one vertical, add some text and watch it bounce around like the DVD screensaver logo.
I remember these from when I initially taught myself HTML (4) and CSS as a kid.
It's kind of amazing how parts of the spec that seem dated or obsolete can still be useful today and are even widely used in corner cases.
Combining it with the referrer tag and you can make some pretty interesting graphs. With frames you can even do Floyd's algorithm.
I made a demo of this about 20 years ago but I think it just confused people. One of my early flops that I thought was cool. It was all in perl and I think there was some JS in there as well but I don't remember anymore. No idea where it is now.
Rewrite it and make a hyped up pitch page. People will call you a genius and I'll pretend not to care
I was so sure archive.is/wip/xxxxxx used this but I just checked and it uses
<script>{setInterval(function(){document.location.reload();},5000)}</script>
now
for example, I tried out view-source:https://archive.fo/wip/RpDSg
does anyone else remember seeing meta refresh? if so, any idea why they switched to javascript reload
Ahh. This brings back memories. I used to do this when I was using Adobe (Macromedia originally) FLASH back in the day. If no FLASH, show them the shitty version. HAHA. Good times.
Sometimes im flabbergasted on how the most basic html knowledge is lost on newer generations.
Ok, I'll bite - how else do people do this? (Speaking as someone who has ONLY ever done it this way.)
I've recently deployed this trick on my company's confluence instance (with an HTML macro) to create a "poor man's" link shortener that allows me to change the link target after the fact.
Also recently deployed it as a very simple server side denounce: when the client first accesses page X a long running operation is dispatched. Subsequent requests for the same resource before it's done processing return a plain HTML response that says "Still thinking about it" and meta refresh after 1 second.
This reminds me of the days of making text adventures that used a width 0 frame to store background variables.
I use
<meta http-equiv="refresh" content="300"> to do speed test from fast.com
see:
view-source:https://angularten.github.io/
I remember when it was released as a new feature (~1995).
Amazing that these were forgotten!
Hehe, the good old html meta redirect. As a kid in the early days of the web I loved to post redirects to porn websites in guestbooks to check if the website was sanitizing the user content properly. Worked way to often :D
This reminds me that while I’ve been programming for a paycheck since 1998 my knowledge growth in html stopped at about 2001. Are there any good courses or recommendations for seasoned pros who never stopped to learn HTML5?
I use this trick to autorefresh the resource that I'm working on.
Putting 0 value used to be a bad idea, as it was a signal to the browser and various ad blockers and anti viruses that it was a rogue redirect. Wonder if it’s different these days?
when they just learned about it was in 2020.
Goddammit!
[flagged]
Noob learns basic HTML tag. The post.
I remember once learning that php has a `header` function and have been using 'location:...' since ever (pre-2000) as php was almost always supported by hosters like dreamhost, hostgator, and nearly every Linux install came pre-installed with Apache and the php mod. The meta htttp-equiv was a last resort (like gh-pages). Never really used the JS option unless it was part of the application.