...

View Full Version : javascript pop-up menu on the older browser



javasam
09-26-2003, 01:56 AM
Hi. I am pretty new at javascript. What are some of the problems for the javascript pop-up menu on the older browser like netscape 4 & up and IE 5 and older computer?

Roy Sinclair
09-26-2003, 04:36 PM
What pop-up menu? It's not like there's only one.

javasam
09-26-2003, 05:07 PM
okay. The Javascript pop-up menu from Dreamweaver MX.

Originally posted by Roy Sinclair
What pop-up menu? It's not like there's only one.

Roy Sinclair
09-26-2003, 07:18 PM
Unless you post the code or a link to a page using the code then someone else will have to help you with the answer since I don't have/use Dreamweaver.

At a guess though, I'd suspect it might work. Have you tried it yourself or are you just trying to find out if anyone knows?

I have NS4 installed for testing so I can definitely check that one and if NS 4 works it's going to be near certain IE 5 will but a peek at the code will tell all.

javasam
09-30-2003, 02:02 AM
Hi, Ron.
Could you check it out for me. Here's the link to the popup menu from Dreamweaver mx . http://www.samhmah.com/popup/menu.html

Spookster
09-30-2003, 02:22 AM
Works in:

IE6.0
NS4.7
NS7.0
Opera7.1
Mozilla 1.4

javasam
09-30-2003, 05:59 PM
Originally posted by Spookster
Works in:

IE6.0
NS4.7
NS7.0
Opera7.1
Mozilla 1.4


Thank you.:thumbsup:
If it works in NS4.7 Does it means if it also work in IE 5

Vincent Puglia
09-30-2003, 09:17 PM
Hi javasam,

knowing the MickeyMouse (dreamweaver) as I do (which is very little, thank god) -- if it's simple enough it will probably runs in everything.

nn4 -- document.layers
ie4 -- document.all
most everyone else -- document.getElementById

so if your *.js file has all three of those phrases, it will work for over 95% of the browsers out there, especially since aol browsers (the one I checked with -- though there was no image for the first menu item) are crippled, but frilly, IE browsers

Vinny

me'
09-30-2003, 10:13 PM
Compliance with version 4 browsers is more of an added extra. Nowhere near necessary - those versions are like 2 years old each. Anyone browsing the web with those must already be awear they're using a dinosaur.

http://www.alistapart.com/stories/netscape/
http://www.alistapart.com/stories/tohell/

Vincent Puglia
09-30-2003, 10:24 PM
Hi me'


Anyone browsing the web with those must already be awear [sic] they're using a dinosaur

true


Nowhere near necessary

To paraphrase what I told someone else at a different forum:
As long as the amount of effort to code for NN4/IE4 is neglible, there is no reason not to and a lot of reasons to do so.

javasam is not putting in any more effort for NN4 compliance than 'standards' compliance -- his mickeymouse wysiwyg editor is doing the work. To remove the code would require work on his part (as well as knowledge he evidently doesn't have -- else he would have known at a glance that it worked for IE & NN).

Being standards compliant does not mean ignoring the older browsers -- and if it does, it's wrong and discriminatory -- the majority of people using the older browsers are probably old, poor, stuck in a bureaucratic mire, and/or 3rd world.

2 years ago, I helped someone script pages for IE3 because some school system in Australia or New Zealand didn't want its students and pta to upgrade.

Vinny

me'
09-30-2003, 10:28 PM
So let me rephrase.

Coding for v4 isn't really worth it, but hey! As long as it's not getting in the way of the rest of your code, or web standards (I wouldn't go as far as using hacks to code for v4s) why not?

brothercake
10-01-2003, 04:37 AM
Originally posted by Vincent Puglia
Being standards compliant does not mean ignoring the older browsers
No it doesn't, but it does mean not providing rich content for them.

Working with XHTML+CSS, it's almost impossible to make a comparable layout in 4-version browsers - and you shouldn't even try - for these browsers a plain, unstyled layout is infinitely more useable.

Vincent Puglia
10-01-2003, 01:29 PM
Hi brothercake,


rich content for them.

I guess it comes down to the definition of 'rich content'.

If I am able to code a layered menu that works for all, why shouldn't I? If I can add elements (inputs) change styles with an extra hour of coding for NN4, should I ignore it? Why do I have to use 'createElement' or 'appendChild' in my script, when 'innerHTML' and 'doc..layers[div].doc..write(txt)' do the same job?


a plain, unstyled layout

There millions of pages out there (on the web) for version 4 browsers that are far from 'plain and unstyled'.


Working with XHTML+CSS, it's almost impossible
The key word is "XHTML", not 'impossible' -- something a lot of today's standards-bearers (to bring new meaning to an old phrase) seem to forget. If the site is not using XHMTL, there is no reason not to support the older browsers with at the least the appearance of 'rich content'.

Vinny

me'
10-01-2003, 06:35 PM
Originally posted by Vincent Puglia
If the site is not using XHMTL, there is no reason not to support the older browsers with at the least the appearance of 'rich content'

If the site's not using XHTML? XML is the way of the future (at least according to w3c, and I'm inclined to agree with them!) so why are you avoiding coding for the future just because it means you can code a little more for the past?

Use XHTML.

Vincent Puglia
10-01-2003, 06:50 PM
why are you avoiding coding for the future just because it means you can code a little more for the past?

I do not avoid coding for the future; I simply do not ignore the past. The code I suggest to people does not hinder Opera, Firebird, etal. A page written solely with 'standards' code, on the hand, does have a good chance of inhibiting NN4 & IE4. If that means the page cannot use XML, etc. -- so be it. Why do I need it? What does it do for the page that already isn't done?

Or, is this a case of wanting what the Jones' have?

Progress should never be used for progress' sake (which is what it sounds like when people scream 'STANDARDS!'). It should be used because it is needed.

Vinny

me'
10-01-2003, 06:55 PM
Progress should never be used for progress' sake (which is what it sounds like when people scream 'STANDARDS!'). It should be used because it is needed.


This is the whole idea of XHTML - stricter type so that more browsers understand the code with less problems!

Coding with XHTML doesn't change how the page looks in v4 browsers.

Vincent Puglia
10-01-2003, 07:09 PM
hi,

if you reread the posts, I'm saying people should not deliberately ignore the older browsers simply because the 'standards' do not allow for them. If version 4s can understand the XHMTL+CSS well and fine; if they cannot, I'll continue to use the older, tried and true code. If that means I can't 'Xwhatever', it's not my loss -- because I'm including 'x' number of surfers -- even if 'x' is only 1, that is 1 more than the site that uses the 'Xwhatever' code. And, it might turn out to be the one individual who actually shops and buys something.


This is the whole idea of XHTML - stricter type so that more browsers understand the code with less problems!

Not quite. The premise is that 'eventually' all browsers will interpret code in the same way and thereby be able to display that code in a similar fashion.

Which is tantamount to what M$ did to the PC OS world.

Vinny

javasam
10-01-2003, 07:35 PM
Thanks Vinny. Now I know what to check next time. The Javascript menu does ineed have those 3 phrases.

Originally posted by Vincent Puglia
Hi javasam,

knowing the MickeyMouse (dreamweaver) as I do (which is very little, thank god) -- if it's simple enough it will probably runs in everything.

nn4 -- document.layers
ie4 -- document.all
most everyone else -- document.getElementById

so if your *.js file has all three of those phrases, it will work for over 95% of the browsers out there, especially since aol browsers (the one I checked with -- though there was no image for the first menu item) are crippled, but frilly, IE browsers

Vinny

me'
10-01-2003, 08:55 PM
Hehe... we kinda clogged up your thread there with our discussion... sorry :D



EZ Archive Ads Plugin for vBulletin Copyright 2006 Computer Help Forum