botheration

[egypturnash]

Okay, dynamically generating frames from the ether was a cool idea, but it does not seem to, like, actually work. Bother.

I should make food.

---

Later in the night.

Oh, lovely. It works fine if I use file:// to access it, with the exception of the tab never deciding to stop saying "Loading"... - but if I go through the web server, I get... next to nothing. Suck! Suck suck suck suck suck.

---

Next morning: oooh, makali pointed me in the right resource direction - noto exactly what I needed, but a few investigative clicks away from exactly what I'm working on. O frabjous moment!

Comments

[kiala.livejournal.com]

Wait.. what are you trying to do?

[shatterstripes.livejournal.com]

New portfolio website that's simple enough to maintain that I might actually do it. I was doing it with CSS, and it worked fine on Moxilla strains and Safari, but IE's just a pain, starting with the fact that I don't have a Windows box to run it on!

So I can have this which looks exactly as I want in Gecko browsers, and pretty mediocre in IE at best, or I can have this, which... well, it was working on my local machine in Camino and Safari, but stopped on Camino at some point, and works on absolutely nothing when taken from a webserver...

...I hate debugging.

[shatterstripes.livejournal.com]

...by the way, that image is so amusingly... you. *giggle*

[kiala.livejournal.com]

Yes it is! =D Would you believe that's a photograph of a wall in DisneyWorld? ;>

[mattlazycat.livejournal.com]

Frames!? ;)

[shatterstripes.livejournal.com]

I was going to use divs with scroll:auto, but IE just vomits all over itself when you ask it to do a liquid layout involving one, and I'd rather do a horribly wrong hack instead of some twisted ugly mangled bit of CSS that makes my code uglier.

Also I don't have any docs handy on doing really dynamic pages with Javascript and modern browsers. Sure, I can swap images, but I want to swap body text around too...

[mattlazycat.livejournal.com]

S'okay, I'm just tugging your tail. I'm entirely too lazy pragmatic myself to hold anyone else to any ideals unless they're crowing about how wonderful their solution is :)

FWIW, it's not just IE that sucks at scroll:auto. Pretty much every browser messes something up, whether it be rendering or scrolling with the mousewheel, etc. I'd avoid them entirely, though I'm not sure I'd go as far as frames. If you have a large dataset and you like playing with the DOM (or hell, even just CSS), you can collapse your data into groups by letter, etc. A List Apart (http://www.alistapart.com/) recently had a neat DOM scripting (http://www.alistapart.com/articles/tableruler/) article about adding a position-marker to tables that might show you some appropriate javascript. Make it a rainy-day thing and get on with your project as it is now though, I think. Le ‘mieux’ est l'ennemi du ‘bon’, as they say.

[shatterstripes.livejournal.com]

Ahhh! The article you pointed to was impenetrable, but a few clicks away I found this which is exactly what I'm trying to implement. Glee! Thank you!

I've never bookmarked List Apart; every time Google takes me there it always seems to be on a page about three- or four-column layouts. People are so obsessed with columnnar layouts in the world of CSS hacking.

[mattlazycat.livejournal.com]

Yes, yes they are. I think it's something to do with CSS being really bad at them and tables being really good at them.