After thinking about it more, I came to the conclusion that I was absolutely right, but very wrong. "They" were not going to change and I (we) was (were) the worse for wear. So better detection was patched into Camino. Absolutely a sad state of affairs, but now we don't have nearly as much of a hassle as we did have.
It has been, and always will be, an issue that the web is infused with a lot of crappy code; especially javascript. If you develop a browser and only point the finger, guess what? Your users lose functionality. And what's the point of spending time creating a browser if most folks get "driven" to use something else that simply works better.
Frankly, I fervently hope that Pink and the guys who write Camino's code take pride in their oh so clever ways of working around others crappy code.
At 11:56 AM -0500 2/8/04, [EMAIL PROTECTED] supposedly scribed:
This is because the javascript code behind the select menu you've pointed to is totally broken. I have no idea what Golive is doing here, but this is some of the JS that forms the jump menu that you pointed to:
<csobj w="158" h="23" t="URLPopup" data="{ 0 = { label = "Tequila Reposado"; selected = "YES"; }; 1 = { label = "1921 Reposado"; url = "retour/1921rep.html"; }; 2 = { label = "1921 Reserva Especial"; url = "retour/1921res.html"; }; 3 = { label = "Aguila"; url = "retour/aguila.html"; }; 4
First of all, there's no such tag in the HTML spec as "csobj" - it's proprietary to Golive. Second of all, if you're creating a jump menu all you need is an onchange action in the form instead of the spaghetti code that Golive spits out.
Do a google for "javascript jump menu" and you'll find scads of examples. I hate to say it, but your problem is one of the many gotchas you can encounter when you let a piece of software do your coding for you.
Short answer: This isn't Camino's fault.
Neil
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
