IE6 bug UL style problem in table

"Randall Sell" <randallsell (AT) nospam (DOT) yahoo.com> wrote:

Thanx, that was very helpful. Although there would appear to be a bug in IE
6 where this technique:
a {display: block;}
li><a href="..." title="...">....</a></li

Does not work when embedded in a <table> (Note, it DOES work if it is in the
first TD, other TDs you need to be over the text itself)

I've had some problems with IE in this area, are any of the containing
elements floated or positioned? That seems to have an effect.
Otherwise, yeah it's a pain when IE gets its knickers in a twist.

I guess I am trying to draw a balance. This HTML is going to be very large -
probably 100k or so after it is dynamically created. so I was trying to keep
the size down by moving redundant code to JavaScript routines.

For example, rather then have
a title="a description that is repeated in many places">my hot text </a

I use Javascript. The above line might appear 200+ times in the HTML report.
So in an attempt to keep the physical file size smaller I use the
onmouseover etc to put in my help hint. I can achieve similar results
(window.status vs title attrib) and save a lot of bytes in terms of overall
file size.

window.status really isn't comparable to title.
Users are much more likely to see the text if it's in a title
attribute - my browser doesn't even have a status bar visible at the
moment.

Considering I have no choice but to use
Javascripting in other areas (and hence required in order for the report to
render correctly) would you still advise on using title="" vs JavaScript?

If I was going a JS heavy route then I would dynamically set the title
attribute rather than set a status bar message. It would only be a
small change to the code you have there already.

But looking at the messages your setting, I wouldn't bother at all.
This is not an application for the general public and so the users
should know basic things such that a link will "Show detailed grader
information."

I do have a NOSCRIPT tag to advise the user they need it turned on.

You need to put the noscript element in the body of the page, not the
head, and the message should be a bit friendlier.

thanx for your input
-randall

ps- care to see the work in progress...
http://www.bytewise.com.au/test/reportwriterproto.html

I get a constant stream of JavaScripr error messages in IE6.

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don't like my tie." - The Doctor

Steve Pugh <steve (AT) pugh (DOT) net> <http://steve.pugh.net/>

"Steve Pugh" <steve (AT) pugh (DOT) net> wrote

"Randall Sell" <randallsell (AT) nospam (DOT) yahoo.com> wrote:

Does not work when embedded in a <table> (Note, it DOES work if it is in
the
first TD, other TDs you need to be over the text itself)

I've had some problems with IE in this area, are any of the containing
elements floated or positioned? That seems to have an effect.
Otherwise, yeah it's a pain when IE gets its knickers in a twist.

There are floating elements in this HTML, although not within the <table>
But it is now somewhat of a moot point as I am not using <a> tags at all.
The onmouseover is working well under both browsers. Just another item to
remember in the "this don't work under IE" list.

But looking at the messages your setting, I wouldn't bother at all.
This is not an application for the general public and so the users
should know basic things such that a link will "Show detailed grader
information."

You are over estimating the intelignece of my users They need as much
hand holding as I can give them.

I do have a NOSCRIPT tag to advise the user they need it turned on.

You need to put the noscript element in the body of the page, not the
head, and the message should be a bit friendlier.

according to
http://www.w3.org/TR/REC-html40/inte...#edef-NOSCRIPT

The NOSCRIPT element allows authors to provide alternate content when a
script is not executed. The content of a NOSCRIPT element
should only be rendered by a script-aware user agent in the
following cases:
The user agent is configured not to evaluate scripts.
The user agent doesn't support a scripting language invoked by
a SCRIPT element earlier in the document.

To play it safe, I placed it before any <script> declaration. It seems to
work fine in the header or in the body.

Ideally, I'd like NOT to render any of the HTML if they don't support
javascript, but don't see a way I can do that easily.

I get a constant stream of JavaScripr error messages in IE6.

Really? I get none. What is your environment? Win2k or WinMe? or NT4? or
other? Mine shows no errors at all. can you copy/paste so I might see? Note
that not all links are complete so there are places you can click that are
technically invalid. it is just a prototype. but most links should be ok.

thanx,
-randall

On Tue, 07 Oct 2003 09:25:42 GMT, "Randall Sell"
<randallsell (AT) nospam (DOT) yahoo.com> wrote:

To play it safe, I placed it before any <script> declaration. It seems to
work fine in the header or in the body.

No, the content of NOSCRIPT is body content, so it must go in the
body, it can't go in the HEAD, as soon as you put any content in it,
in HTML the HEAD will end and the BODY begin, or in XHTML you'll just
get an error.

Jim.
--
comp.lang.javascript FAQ - http://jibbering.com/faq/