Conversion to Netscape a Netmare!

too many events to deal with....

[txbakers]

Could someone with some patience please take a look at an ASP page which is jolly good in IE, but won't even load in NS?

I'll buy you lunch.....

[caine]

sorry tx, dont have the time to go into your code, though what i can suggest, is trying the validation service, either from Bretts sister site SEW (link top right), or directly at www.w3c.org. Maybe the wysiwyg that you used isn't doing the HTML spot on, also does the page resolve in Opera, as this is definetly an up and coming browser, and as people (comp-literate) are trying to get away from MS OS's (cost and lack of security), its definetly one to watch.

[txbakers]

Thanks for the suggestion. I did run one page through the Validator at w3C and gave up.

The amount of "errors" due to my ASP code made the exercise moot. All the response.write options caused hanging tags, duplicate tags, unclosed tags, etc. The Validator doesn't read the ASP code, so it thought the site was full of errors.

My market is schools, so Opera is a non-issue. My W2000 thinks Opera is Netscape anyway, and I think the Mozilla engines are very similar. I'll not worry about Opera for this release.

I'd prefer not to support Netscape also, but for now I'll get it working.

Absurd.

[gethan]

Put the exact page in your profile and I'll take a glimpse.. (no promises on a fix)

The things that I get tripped up by in NS vs IE are:

Tables -- NS much fussier - needs every /tr, /td and /table
Javascript -- DOM is very different.

They're the 2 most obvious things to start with

Good luck

Gethan

[txbakers]

Thanks Gethan - through the night I was able to fix many of the Netscape issues.

they mostly revolved around not using A href tags on images, (instead I would do the Mouseover, onClick, etc. directly on the img tag).

That fixed a bit. I put in the missing   code in some of the cells, which IE could figure out but Netscape couldn't, and found a better JS code for reading the value of select lists. Netscape's method was so counter-intuitive. So for now, I'm back on track.

I'll put the site link in the profile, but it's all ASP - you'll need to come in through the front door or it won't work.

THANKS

[Woz]

TXB,

it will be the resultant page post server that has the errors not, not the asp page pre server. You need to save the page you see in your browser and then run that through the validator. Your ASP code is in itself irrelevant as browsers never see it, only the results.

Onya
Woz

[txbakers]

Right! I sometimes forget that.

Run the page, View and Save source, then validate!

Pants first, then shoes.