"And the beast shall come forth surrounded by a roiling cloud of vengeance. The house of the unbelievers shall be razed and they shall be scorched to the earth. Their tags shall blink until the end of days." > from The Book of Mozilla, 12:10 (about:mozilla) And now Mozilla is being scorched to the earth. The End.
I don't know, I still use Firefox as my primary browser.
and (2020)
41–50 of 191 posts
Re: <Blink> and <Marquee> (2020)
#42Re: <Blink> and <Marquee> (2020)
#43Ah yes, the to tell everyone the website made in notepad in 1997 was still under construction in bold, Comic Sans, and fuchsia on a yellow background. Don't forget the lots of NBSPs so that the message scrolls off for even a longer period of time and the reader has to wait for their computer to shift the message back into the viewport. What's missing about the retro experience is browsers and computers were slower ba…
Image of a construction worker digging
Re: <Blink> and <Marquee> (2020)
#44I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…
>Who here remembers frames? I visit a site with frames several times a week. Nobody's ever told the Open Group/POSIX people they're not supposed to use them these days.
Re: <Blink> and <Marquee> (2020)
#45Earlier quoted context omitted.
I made a webchat with frames; an infinitely-loading top part for the text, and the bottom an input box that received 204 to not reload when you sent a message. I guess that was the most elegant way to do it in the IE4+ days. The top part could also receive a small that would reload the frame on the right, containing the user list. Fun times. Used it with a couple class mates around 2000 iirc.
I managed to get real-time chat (and other real-time colab) working on IE4+ using long polling, by continuously adding tags from JavaScript. The server would delay answering until there were new messages available, or some timeout. This was even before xmlhttprequest. Who needs websocket? :-)
Re: <Blink> and <Marquee> (2020)
#46I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…
3000 years ago, when Ancient Egyptians argued over how they should format Papyrus text.
Re: <Blink> and <Marquee> (2020)
#47Considering the marquee tag works in basically all browsers [1], has anyone here actually found a good, unironic use for it in today's world of crazy CSS animations? [1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
I never figured out why the actual tag has a low frame rate. Maybe it’s to make it more unpleasant so you won’t want to use it. Certainly I would use a CSS animation instead for the frame rate reason, if I was forced to put a marquee on a page.
Re: <Blink> and <Marquee> (2020)
#48Re: <Blink> and <Marquee> (2020)
#49Re: <Blink> and <Marquee> (2020)
#50I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…
To export gifs meant to be positioned perfectly in HTML tables
For designs suited best for 800x600
All those moments lost in time, like tears in the rain