Wednesday, July 12, 2006

bad code

there's some bad code in one of the sibel interview posts, and i haven't been able to track it down.

it makes Opera go all spazzy - but it looks ok in my firefox and IE.

is anyone else having probs?

12 comments:

Anonymous said...

At least in part three there are dozens of consecutive font/span tags around some sentences, totaling over 2000 unnecessary tags. I guess this is due to over copy/pasting that tries to preserve formatting. You can check the source and search for <font><font><font>

lukery said...

thnx teemu.

it seems to be something to do with Blogger - it keeps generating them like crazy, even when i take them out

Anonymous said...

I have no idea if this is your site or just what, but it is REALLY slow. Could those taggy thingies cause this? Trying to scroll down the page is excruciatingly, painfully pokey. Worse than a crawl. Other windows open at DKos and elswhere are running normally. ??? Otherwise, it has a normal appearance in IE.

lukery said...

lee - yeah - there's something wrong with those posts. grrrrr.

i'll try to get them off the front page in the next couple of days.

Anonymous said...

Have a lovely time. ;-)

Oy.

lukery said...

egads.

lee - is the front page still slow?

teemu helped me out with the code and it *appears* to be a bit better

Bukko Boomeranger said...

Still taking an inordinately long time to load @ 1900 AEST.

lukery said...

argh - i didnt know that there was a loading problem as well. apparently there's a dodgy 'script' or something in there somehow. i actually back-dated a bunch of new posts to keep them off the front page becuase it appeared that there were problems with those too.

if you can bare with me for a day or two - and then i'll remove those interview posts from the front page.

i'm also in the process of shortening my front page from 8 days to 3 days - so hopefully that might help.

does anyone come here just once a week? i wouldnt think so.

Anonymous said...

Well, well! I see it didn't take you two or three days to fix it! Good job. Now it is running normally. Hope that's true for everybody else.

A bit OT, but something that would certainly help keep this US poster better grounded about chronology is the time stamps on these comment posts . . . is there an option to add the date to that bit? When a thread lasts over several days, I end up royally confused on how long ago somebody last jumped in (like, has the discussion moved on so don't bother?). At this moment, f'rinstence, it is a bit after 8:00 p.m. U.S. Pacific Daylight Time. When this bit goes up, I'll be able to see what time it is on this blog, but is it still July 12? Argh! I'm always in a silly time-warp! :-(

lukery said...

yeah - i couldnt fix it - so i just pushed all those interview posts off the front page.

i agree about the comments - i dont know how to add the date. it does suck. re the timestamp, i think it actually stamps it with my time - ie australia - so that doesnt help much either.

Anonymous said...

if you can bare with me for a day or two

you do mean to strip down, right? count me in. :-)

lukery said...

lol - yep - i did say 'bare' - you and i must have the same thing on our mind...