BURNINGBIRD
a node at the edge  


May 04, 2002
TechnologyOverlapping Images

I've had entries in my comments in addition to email that the images are overlapping the text when my new weblog is viewed in Netscape 4.7.

This is not an unknown problem with Netscape 4.7 and usually has to do with wrapping the IMG tag in paragraph tags. This is also further complicated by the use of the CSS attribute LINE-HEIGHT.

I've experimented around with one of the postings -- removing the line-height attribute from the surrounding DIV block, removing automatically generated line breaks so that I can use my own formatting and so on, but from what I can see in Netscape 4.7 on my Linux box, the images are still overlapping the text.

I have the following options at this time:


  1. I can go back to Blogger and forget all about Movable Type because this problem didn't occur with Blogger.
  2. I can change the formatting on this new blog to emulate what I had in Blogger, completely.
  3. I can stop using images.
  4. I can leave things as they are, continue to look for a solution, and hope that all the Netscape 4.7 people will:

    1. Understand these things happen when you use an old browser and
    2. Consider upgrading or
    3. Realize that they're going to have these problems and adopt a philosophical approach to the whole thing.

At this time, I'm following the last option.

For more on Overlap Problem:

Fear of Style Sheets 2


Posted by Bb at May 04, 2002 05:03 AM




Comments

I think I'd have to agree that 3 may be the best option. I'm using Mozilla (what Netscape has become :)) and things look great here.

Posted by: Will Leshner on May 4, 2002 08:45 AM

What I fail to understand is why people insist on using old browsers...

One thing I was going to pursue was to try and figure out if there would be a way to generate a 'low-fi', style-sheet-less version of my MT blog, along with the regular one, every time I post or rebuild.

I suspect not, at least without some hacking of the MT code. That's a bigger project than I wanna get into...

Posted by: stavrosthewonderchicken on May 4, 2002 07:21 PM

I, for one, am sick of trying to code for all browsers and especially that ageing waste of time call NN4.7.

It's not just the hassle, its the knowledge that you're tweaking code for viewers who probably don't have a clue anyway.

There's no way I'd embrace option '3' as proposed by Will. - how can I as a photographer not include images? [Except I have a feeling he might have meant sub-option 3 in option 4 ;-) ]

The obvious way to go is '4'. Eventually the message will get through. NN4.7 users are slowly fading away according to all the major site statistics.

When NN4.7 users made up at least 10% of the stats, I had to agree with the effort needed. But statistics I saw yesterday indicated this had dropped to less than 2%.

Posted by: Allan on May 4, 2002 07:47 PM

I'd be curious to hear from people about why they haven't upgraded. Especially with Mozilla 1.0 RC.

Posted by: Bb aka Shelley aka Weblog Bosswoman on May 4, 2002 08:11 PM

Being a member in good standing of the "Bill Gates and Microsoft are Evil" club, I've been a loyal Netcape user since day 1. As soon as NS 6.1 came out I upgraded. I'm now running 6.2 and your page looks great in it.

I don't understand why those who prefer to use NS don't get the new version.

I'm using the "Tanek hack" and an imported style sheet on my site and giving the old browser users basically an unformatted page. It looks blah, but the can still read it.

Posted by: Kath on May 5, 2002 12:54 PM

Go with option 5 - use @import to import the style sheets (thus NS4 won't know how to load them but modern browsers will) and try to make the site look readable in NS4 when no style sheets are loaded.

Posted by: Simon Willison on May 6, 2002 05:37 AM

Simon, that is still basically a hack -- and extra work. Not many web designers can afford that extra effort and cost, especially for their smaller clients.

Posted by: Allan on May 6, 2002 03:41 PM

I disagree, Allan. As long as you design your site properly from the start, you shouldn't even have to worry about the extra effort at all. It should just work.

My site uses the tantek box model hack, which, because it uses a backslash, prevents Netscape 4 from parsing the stylesheet, yet it is still perfectly readable in Netscape 4.x, as well as all the browsers created before stylesheets were even thought of.

Posted by: Lachlan on May 25, 2002 08:53 PM


Post a comment

Name:


Email Address:


URL:


Comments:


Remember info?