The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

i am not trying to find out if the user has javascript or not...
i will assume that they do. but - i don't want to exclude the few folks that visit without javascript. those with javascript will get a nicely formatted window sized to my specs. those without javascript will get a new window using plain ol' HTML (target="newWindow").

this method works for the most part... but it has a few problems (for example... in NS6 mac it opens the popUp and targets a new window). I just want to see if there is a better way.

Originally posted by Jack Michaelson It seems to me that you can't find out if someone has js or not by using js. Not sure though.
I think you have to use something else (ie. PHP) than Javascript to detect wether the user has js or not.

If he does: pop-up script
if he doesn't: new window script.

Does this help?

You can detect where someone has js on. You can do this in a variety of ways, using serverside and clientside,

that may be true for the web population in total... but i often deal with a specific user group that is much higher...
blind folks using lynx for instance... and upgrade won't help them...

---

to the person that mentioned testing to see if someone has js enabled...
i've used a solution where the js hid a <div> containing navigation for those without js - at the same time I had it write a new <div> containing the fancy pants version for those that did have js. so if the js wasn't enabled the default <div> couldn't be hidden and the fancy one couldnt be written...
it wasn't testing so to speak... but it easily did the job.

i've also done similar things with "display:none" in my css to show and hide info from browsers..

just make sure you know how things break and you can find away to make it work.