Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

and (2020)

danq.me

Post reply on HN
Print view View original

121–130 of 191 posts

Re: <Blink> and <Marquee> (2020)

#121

Post by joshuaissac »

bornfreddy wrote: post #111
ripdog wrote: post #74

Earlier quoted context omitted.

Um, so, how are Mozilla supposed to get the hundreds of millions of dollars a year it costs to pay engineers to maintain an evergreen browser without Google's funding?

How did they survive without their funding before they got it? And don't say that web standards are much more complex nowadays - yes, they are, because it is in Google's interest to make them such. Will it hurt? Yes. Will Firefox survive? I hope so. Is it a bad idea? No.

> How did they survive without their funding before they got it?

They were initially Netscape, a commercial company, so they had money from their customers.

After the browser code base was handed over from Netscape/AOL to the Mozilla Foundation in 2003, they got donations from AOL, IBM, Red Hat, etc. which kept them going for a few more years.

The Mozilla Foundation signed the deal with Google two years later, in 2005.

In short, they survived first on commercial revenues and then from donations, neither of which are substantial now.

Re: <Blink> and <Marquee> (2020)

#123

Post by davidmurdoch »

rdrd wrote: post #84
donatj wrote: post #21

I 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…

I remember working for a client who needed to support IE6 (with all the insane bugs/quirks/limitations) and I’d despair every time the designers would hand over a Photoshop design with rounded corners. They also needed it to be responsive (at the time mostly just different desktop sizes). Would usually require cutting the corners out and positioning them in table cells. There’s a certain amount of dev resilience you…

For some reason I actually really loved doing this. I remembering feeling disappointed when css got border radius.

Re: <Blink> and <Marquee> (2020)

#124

Post by MyPasswordSucks »

Timwi wrote: post #73
donatj wrote: post #21

I 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…

I developed web software with frames and I thought it was perfectly fine. To this day I still don't understand the issue with frames. People sometimes mention accessibility for screen readers, but nothing more specific than that, so I still don't know what the actual problem is.

> I still don't understand the issue with frames.

I paid for 1024x768. Because of your frames, the content I'm actually interested in is now restricted to some disgusting and dismaying fraction of that. The borders of my bitchin' 15" CRT are now committed to navigation (which I have to scroll horizontally to actually make sense of) and what is likely a LinkExchange banner on the bottom that adds absolutely nothing to my experience.

Re: <Blink> and <Marquee> (2020)

#125

Post by codingdave »

jameslk wrote: post #50
donatj wrote: post #21

I 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…

I remember meticulously using the photoshop slice tool 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

That is what Fireworks was great for: https://en.wikipedia.org/wiki/Adobe_Fireworks

Re: <Blink> and <Marquee> (2020)

#126

Post by okanat »

echelon wrote: post #104
Timwi wrote: post #73

Earlier quoted context omitted.

I developed web software with frames and I thought it was perfectly fine. To this day I still don't understand the issue with frames. People sometimes mention accessibility for screen readers, but nothing more specific than that, so I still don't know what the actual problem is.

We should have frozen the web from 2006 - 2010 or so. We had Ajax, lots of modern CSS, but weren't hell-bent on CSSifying and "SPA"-ing everything. Web standards hadn't yet jumped the shark. It's also before Steve Jobs murdered Flash. Killing Flash was one of the biggest mistakes we've made. The modern HTML/CSS/JS stack can't replicate how simple and functional it was. We're easily dealing with 100x the complexity no…

Flash was a bigger privacy hole than HTML5 canvas. I think we need to mandate browsers that block those APIs on default and only enable them via permission. is often used in fingerprinting. So blocking its introspection APIs would already benefit us.

Re: <Blink> and <Marquee> (2020)

#127

Post by ComplexSystems »

xnx wrote: post #76
Timwi wrote: post #73

Earlier quoted context omitted.

I developed web software with frames and I thought it was perfectly fine. To this day I still don't understand the issue with frames. People sometimes mention accessibility for screen readers, but nothing more specific than that, so I still don't know what the actual problem is.

All content on the web should have a unique, linkable, URL. Frameset breaks that.

That ship has long since sailed. We live in a world of web apps with dynamically created content, AJAX, and so on. The main entry point for the app has a URL, and then within the app all bets are off. Same with framesets.

Re: <Blink> and <Marquee> (2020)

#128

Post by inquirerGeneral »

torgoguys wrote: post #108
atesti wrote: post #91

Earlier quoted context omitted.

If you right click a link and open in new window (or middle click), the frameset was gone and only the piece in the frame was visible. Also you could not bookmark anything. I remember doing a frameset per content frame url automatically and also redirecting to that frameset from inside the page via javascript if the content frame's url was directly opened.

Framesets were great. >If you right click a link and open in new window (or middle click), the frameset was gone and only the piece in the frame was visible. Feature, not bug in my book. Same thing happens in today's iframes. But for situations where that is a problem, the spec could have been extended to support every page being able to identify a preferred parent frame. Or browsers could have changed behavior to by…

[dead]

Re: <Blink> and <Marquee> (2020)

#129

Post by 9rx »

latchkey wrote: post #2

Do you remember when there was a brief bug in Netscape that enabled multiple tags to effectively animate the window title? That was a fun one.

In a similar vein, the little animated messages in the status bar was peak internet.

Re: <Blink> and <Marquee> (2020)

#130

Post by SoftTalker »

rdrd wrote: post #84
donatj wrote: post #21

I 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…

I remember working for a client who needed to support IE6 (with all the insane bugs/quirks/limitations) and I’d despair every time the designers would hand over a Photoshop design with rounded corners. They also needed it to be responsive (at the time mostly just different desktop sizes). Would usually require cutting the corners out and positioning them in table cells. There’s a certain amount of dev resilience you…

Or just telling the designers "we can't do rounded corners for this client" (the client likely didn't care at all).
Post reply on HN