|
|
|
 | |
|
\
\
> \
\
> \\
\
Oh, I previewed and see that **PaulYeah** has suggested something similar and better (DIVs don’t work properly in Netscape anyway). [http://hotwired.lycos.com/webmonkey/](http://hotwired.lycos.com/webmonkey/) is a very good resource for this sort of thing.
---
I am not sure what the problem is but what you have ais a JPG in the background and a title.GIF with transparent background superimposed over it. To me the whole thing is acting normal. Where’s the problem?
---
Thanks guys… gave the CSS route a shot, and it’s still loading like standard encoding.
Maybe the fact that they’re all less than 30k has something to do with it… anybody have any idea how much information is supposed to load on the first pass? That doesn’t make sense though… when you look at the images directly:
[http://neussubjex.net/reds/1.jpg](http://neussubjex.net/reds/1.jpg)
[http://neussubjex.net/reds/2.jpg](http://neussubjex.net/reds/2.jpg)
etc.
They load progressively.
I suppose I could try IFRAME and ILAYER to see if they work. Or I could just compress them more to make them them load faster.
Thanks for going to all the trouble.
**sailor:**
When you save JPEGs in most decent image editors, you usually have the option to make encode them as “standard” or “progressive.” The browsers will load the standard image line by line, while it _should_ load the progressive images in several passes of increasingly better resolution. First, you see an ill-defined mosaic, then the image gradually begins to take shape as it loads.
For some reason, my progressively encoded images are loading like standard when they’re used as a background. Not really a big deal, but I’m an obsessive-compulsive hand coder. Maybe I should just let it go.
\
Oh, I previewed and see that **PaulYeah** has suggested something similar and better (DIVs don’t work properly in Netscape anyway). [http://hotwired.lycos.com/webmonkey/](http://hotwired.lycos.com/webmonkey/) is a very good resource for this sort of thing.
---
I am not sure what the problem is but what you have ais a JPG in the background and a title.GIF with transparent background superimposed over it. To me the whole thing is acting normal. Where’s the problem?
---
Thanks guys… gave the CSS route a shot, and it’s still loading like standard encoding.
Maybe the fact that they’re all less than 30k has something to do with it… anybody have any idea how much information is supposed to load on the first pass? That doesn’t make sense though… when you look at the images directly:
[http://neussubjex.net/reds/1.jpg](http://neussubjex.net/reds/1.jpg)
[http://neussubjex.net/reds/2.jpg](http://neussubjex.net/reds/2.jpg)
etc.
They load progressively.
I suppose I could try IFRAME and ILAYER to see if they work. Or I could just compress them more to make them them load faster.
Thanks for going to all the trouble.
**sailor:**
When you save JPEGs in most decent image editors, you usually have the option to make encode them as “standard” or “progressive.” The browsers will load the standard image line by line, while it _should_ load the progressive images in several passes of increasingly better resolution. First, you see an ill-defined mosaic, then the image gradually begins to take shape as it loads.
For some reason, my progressively encoded images are loading like standard when they’re used as a background. Not really a big deal, but I’m an obsessive-compulsive hand coder. Maybe I should just let it go.