top | item 46186378

(no title)

manbash | 2 months ago

Ah, those days, where you would slice your designs and export them to tables.

discuss

order

chrisweekly|2 months ago

I remember building really complex layouts w nested tables, and learning the hard way that going beyond 6 levels of nesting caused serious rendering performance problems in Netscape.

JimDabell|2 months ago

I remember seeing a co-worker stuck on trying to debug Netscape showing a blank page. When I looked at it, it wasn’t showing a blank page per se, it was just taking over a minute to render tables nested twelve deep. I deleted exactly half of them with no change to the layout or functionality, and it immediately started rendering in under a second.

shomp|2 months ago

Six nesting levels for tables? Cool, what were you making?

reconnecting|2 months ago

Why not! We did this in 2024 for our website (1) to have zero CSS.

Still works, only Claude can not understand what those tables means.

1. https://www.tirreno.com

lewiscollard|2 months ago

That's a fun trick, but please consider adding ARIA roles (e.g. role="presentation" to <table>, role="heading" aria-level="[number]" to the <font> elements used for headings) to make your site understandable by screen readers.

danielbarla|2 months ago

> Why not!

Responsive layout would be the biggest reason (mobile for one, but also a wider range of PC monitor aspect ratios these days than the 4:3 that was standard back then), probably followed by conflating the exact layout details with the content, and a separation of concerns / ease of being able to move things around.

I mean, it's a perfectly viable thing if these are not requirements and preferences that you and your system have. But it's pretty rare these days that an app or site can say "yeah, none of those matter to me the least bit".

thecr0w|2 months ago

I learned recently that this is still how a lot of email html get generated.

mananaysiempre|2 months ago

Apparently Outlook (the actual one, not the recent pretender) still uses some ancient WordHTML version as the renderer, so there isn’t much choice.

ricardonunez|2 months ago

Oh yeah, recently I had to update a newsletter design like that and older versions of outlook still didn’t render properly.

ralferoo|2 months ago

It was relatively OK to deal with when the pages were created by coders themselves.

But then DreamWeaver came out, where you basically drew the entire page in 2D and it spat out some HTML tables that stitched it all back together again, and the freedom it gave our artists in drawing in 2D and not worrying about the output meant they went completely overboard with it and you'd get lots of tiny little slices everywhere.

Definitely glad those days are well behind us now!

dylan604|2 months ago

wasn't it Fireworks that sliced the image originally. you'd then be able to open that export into Dreamworks for additional work. I didn't do that kind of design very long. Did Dreamworks get updated to allow the slicing directly bypassing Fireworks?

mmanfrin|2 months ago

I yearn for those days. CSS was a mistake. Tables and DHTML is all one needs.

thomasz|2 months ago

You jest, but it took forever to add somewhat intuitive layout mechanism to css which allowed you to do what could be done easily with html tables. Vertically centering a div inside another was really hard, and very few people understood the techniques you would use, instead of blindly copying them.

It was beyond irony that the recommended solution was to tell the browser to render your divs as a table.

bluSCALE4|2 months ago

CSS was a mistake? JavaScript was a mistake, specifically JavaScript frameworks.

jweir|2 months ago

And use a single px invisible gif to move things around.

But was Space Jam using multiple images or just one large image with and image map for links?

bot403|2 months ago

The author said he had the assets and gave them to Claude. It would be obvious if he had one large image for all the planets instead of individual ones.

bigbuppo|2 months ago

Oh man, Photoshop still has the slice feature and it makes the most horrendous table-based layout possible. It's beautiful.