tabs, disclosure triangles & alpha transparency

Could anyone please tell me how to fix the following three
IE problems on a website? I don't have a Windows computer
so it's not easy for me to fix. My first problem is a
simple tab implemented by:

<a href="#N">N</a>

that does not work in IE (even IE7) for some reason. If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page.
That page is at:

http://128.111.108.101/index

The CSS is at:

http://128.111.108.101/library/css/surfmaker.css

Another problem is disclosure triangles that don't click down in IE7
but do click down in Safari & Firefox on OSX. This page is at:

http://128.111.108.101/sitemap

The related Javascript is at:

http://128.111.108.101/library/javascript/surfmaker-dt.js

(which I think was obtained from this ng via a post that I read)

and the publicly-available:

http://128.111.108.101/library/javascript/surfmaker-jquery.js

My third and last problem is IE5.5 and IE6 and alpha transparency.
It seems that there is no real solution to this or am I wrong?
I'll take any JS or CSS solution (other than replacing all my
transparent PNGs with transparent GIFs).

This alpha transparency problem occurs on almost every page on the
site.

Thanks a bunch for any help you can provide. Any criticisms of this
website
are welcome but my primary concern right now are the problems
discussed above.

paris2venice (AT) gmail (DOT) com wrote:

Could anyone please tell me how to fix the following three
IE problems on a website? I don't have a Windows computer
so it's not easy for me to fix. My first problem is a
simple tab implemented by:

a href="#N">N</a

that does not work in IE (even IE7) for some reason. If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page.
That page is at:

http://128.111.108.101/index

The CSS is at:

http://128.111.108.101/library/css/surfmaker.css

This doesn't have anything to do with stylesheets. I'm thinking that IF
you use an <a> as your destination, IE7 only recognizes the name
attribute, and you are using ID. On the other hand, if you skip the
empty <a> elements altogether and add the id to the h2 instead, it
should work. On the other hand I don't recall whether linking to
anything other than an <a> works in IE6. If not, then leave the <a>
tags, but give them a name attribute as well.

I'm also thinking that it took my IE7 over a minute to download
something like 200 items. That might not be a good idea.

Another problem is disclosure triangles that don't click down in IE7
but do click down in Safari & Firefox on OSX. This page is at:

http://128.111.108.101/sitemap

The related Javascript is at:

http://128.111.108.101/library/javascript/surfmaker-dt.js

(which I think was obtained from this ng via a post that I read)

and the publicly-available:

http://128.111.108.101/library/javascript/surfmaker-jquery.js

That makes this a question for a jQuery forum.

On Jan 13, 10:03*am, Harlan Messinger
<hmessinger.removet... (AT) comcast (DOT) net> wrote:

paris2ven... (AT) gmail (DOT) com wrote:
Could anyone please tell me how to fix the following three
IE problems on a website? I don't have a Windows computer
so it's not easy for me to fix. *My first problem is a
simple tab implemented by:

* *<a href="#N">N</a

that does not work in IE (even IE7) for some reason. *If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page.
That page is at:

* *http://128.111.108.101/index

The CSS is at:

* *http://128.111.108.101/library/css/surfmaker.css

This doesn't have anything to do with stylesheets. I'm thinking that IF
you use an <a> as your destination, IE7 only recognizes the name
attribute, and you are using ID. On the other hand, if you skip the
empty <a> elements altogether and add the id to the h2 instead, it
should work. On the other hand I don't recall whether linking to
anything other than an <a> works in IE6. If not, then leave the <a
tags, but give them a name attribute as well.

Thanks. I'll try that.

I'm also thinking that it took my IE7 over a minute to download
something like 200 items. That might not be a good idea.

Do you use a dialup modem? Because it's mostly text with images all
under 19k, it loads quite fast on my 3-4 mbits/sec cable modem.
I appreciate the feedback -- what would you suggest as an alternative?
Separate pages for 0-9, A-I, J-R and S-Z or ...?

Another problem is disclosure triangles that don't click down in IE7
but do click down in Safari & Firefox on OSX. *This page is at:

* *http://128.111.108.101/sitemap

The related Javascript is at:

* *http://128.111.108.101/library/javascript/surfmaker-dt.js

(which I think was obtained from this ng via a post that I read)

and the publicly-available:

* *http://128.111.108.101/library/javascript/surfmaker-jquery.js

That makes this a question for a jQuery forum.

In article
<7e6da6f9-61fe-460d-81c5-be71351fca3f (AT) i18g2000prf (DOT) googlegroups.com>,
paris2venice (AT) gmail (DOT) com wrote:

Could anyone please tell me how to fix the following three
IE problems on a website? I don't have a Windows computer
so it's not easy for me to fix. My first problem is a
simple tab implemented by:

a href="#N">N</a

that does not work in IE (even IE7) for some reason. If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page.
That page is at:

http://128.111.108.101/index

The CSS is at:

http://128.111.108.101/library/css/surfmaker.css

Another problem is disclosure triangles that don't click down in IE7
but do click down in Safari & Firefox on OSX. This page is at:

http://128.111.108.101/sitemap

The related Javascript is at:

http://128.111.108.101/library/javascript/surfmaker-dt.js

(which I think was obtained from this ng via a post that I read)

and the publicly-available:

http://128.111.108.101/library/javascript/surfmaker-jquery.js

My third and last problem is IE5.5 and IE6 and alpha transparency.
It seems that there is no real solution to this or am I wrong?
I'll take any JS or CSS solution (other than replacing all my
transparent PNGs with transparent GIFs).

This alpha transparency problem occurs on almost every page on the
site.

Thanks a bunch for any help you can provide. Any criticisms of this
website
are welcome but my primary concern right now are the problems
discussed above.

Not sure where to start. You have over 300 validation errors, many of
which occur because you are using XHTML constructs like self closing
tags ( />) within an HTML document. You have some ID="1" or similar,
however ID has to commence with a letter. You have some <a ID="N"> tags
that never seem to get closed. If IE7 really can not cope with ID, you
can then add name.

Why not go through the validation errors first, and then see what
browsers make of it?

--
http://www.ericlindsay.com

paris2venice (AT) gmail (DOT) com wrote:

On Jan 13, 10:03 am, Harlan Messinger
hmessinger.removet... (AT) comcast (DOT) net> wrote:
paris2ven... (AT) gmail (DOT) com wrote:
a href="#N">N</a
that does not work in IE (even IE7) for some reason. If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page.
That page is at:
http://128.111.108.101/index

add the id to the h2 instead, it
should work. On the other hand I don't recall whether linking to
anything other than an <a> works in IE6.

FYI, linking to an ID should work fine in IE6. The only browser I
remember not supporting ID is Netscape 4.

I'm also thinking that it took my IE7 over a minute to download
something like 200 items. That might not be a good idea.

Do you use a dialup modem? Because it's mostly text with images all
under 19k,

Page info from Firefox: 278.64 KB (285,332 bytes)

Or did you mean each image was under 19k? It took a good 30 seconds
to load for me, and there was probably 10 seconds of blank screen before
*anything* showed.

--
Berg

paris2venice (AT) gmail (DOT) com wrote:

On Jan 13, 10:03 am, Harlan Messinger
hmessinger.removet... (AT) comcast (DOT) net> wrote:
paris2ven... (AT) gmail (DOT) com wrote:
Could anyone please tell me how to fix the following three
IE problems on a website? I don't have a Windows computer
so it's not easy for me to fix. My first problem is a
simple tab implemented by:
a href="#N">N</a
that does not work in IE (even IE7) for some reason. If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page.
That page is at:
http://128.111.108.101/index
The CSS is at:
http://128.111.108.101/library/css/surfmaker.css
This doesn't have anything to do with stylesheets. I'm thinking that IF
you use an <a> as your destination, IE7 only recognizes the name
attribute, and you are using ID. On the other hand, if you skip the
empty <a> elements altogether and add the id to the h2 instead, it
should work. On the other hand I don't recall whether linking to
anything other than an <a> works in IE6. If not, then leave the <a
tags, but give them a name attribute as well.

Thanks. I'll try that.
I'm also thinking that it took my IE7 over a minute to download
something like 200 items. That might not be a good idea.

Do you use a dialup modem?

No, I'm in an office with a T3.

Because it's mostly text with images all
under 19k,

Still, it's 200 separate requests to the server.

On Jan 13, 1:47*pm, Harlan Messinger
<hmessinger.removet... (AT) comcast (DOT) net> wrote:

paris2ven... (AT) gmail (DOT) com wrote:
On Jan 13, 10:03 am, Harlan Messinger
hmessinger.removet... (AT) comcast (DOT) net> wrote:
paris2ven... (AT) gmail (DOT) com wrote:
Could anyone please tell me how to fix the following three
IE problems on a website? I don't have a Windows computer
so it's not easy for me to fix. *My first problem is a
simple tab implemented by:
* *<a href="#N">N</a
that does not work in IE (even IE7) for some reason. *If an IE user
clicks on the href (tab), it doesn't take him/her up or down the page..
That page is at:
* *http://128.111.108.101/index
The CSS is at:
* *http://128.111.108.101/library/css/surfmaker.css
This doesn't have anything to do with stylesheets. I'm thinking that IF
you use an <a> as your destination, IE7 only recognizes the name
attribute, and you are using ID. On the other hand, if you skip the
empty <a> elements altogether and add the id to the h2 instead, it
should work. On the other hand I don't recall whether linking to
anything other than an <a> works in IE6. If not, then leave the <a
tags, but give them a name attribute as well.

Thanks. *I'll try that.
I'm also thinking that it took my IE7 over a minute to download
something like 200 items. That might not be a good idea.

Do you use a dialup modem?

No, I'm in an office with a T3.

*Because it's mostly text with images all
under 19k,

Still, it's 200 separate requests to the server.

I really appreciate your concern about it and I was aware of it before
posting here. But, just so you know, the website is really not
intended for the entire world's consumption and it wasn't until
recently. It's just for our Department. What made me decide to open
it up (by taking away the "deny from all" with a few "allow from"
statements) is that I could never comprehensively add all the "allow
from" statements. Even now, some of the site remains password-
protected. And it loads very quickly everywhere in our Department so
there's not a whole lot of motivation for me to modify that one page
among the nearly 200 others. And ... it is an index. How else should
it be done?

Still, thanks for the constructive criticism.