I have an onkeypress routing in an input field within a table. If I use WIDTH="640" in the TABLE tag, the table displays great but the onkeypress event won't fire. If I use WIDTH="100%", the event will fire but the display isn't right. It gets better. If I adjust the input cell TD with WIDTH="60%", the display is corrected but the event will no longer fire. All of these problems are observed in Netscape 4.7 but not in IE. Any suggestions?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
onkeypress in fixed-size table (Netscape) 1
- Thread starter RoryMcQ
- Start date
-
1
- #3
- Thread starter
- #4
- Thread starter
- #5
You can view my code at - <A HREF=" TARGET="_new">
Dear Rory,<br><br>From your code:<br><br><input type="radio" name="dems" value="1" onclick="setAmt(document.SchedCP.AmtContrDemParty,1)"><br><br>Your onclick event is set to call a function named 'setAmt'. There is no function named 'setAmt' in the page. <br><br>If this is NOT the problem you are trying to solve, then you need to try much harder to explain the problem and reduce the code to the MINIMUM amount to produce the problem.<br><br>"But, that's just my opinion... I could be wrong".<br>-pete
- Thread starter
- #7
Ok, you have a point, that occurred to me after I put the code up. I believe I have now removed all references to non-existent routines & Netscape still isn't firing the onKeyPress event, while IE is. The code is still at<br><br>
Rory,<br> First of all, Netscape is very intolerant of errors in your code. In your case, inside the script tag, you need to change --> to //--> so it doesn't get processed as Javascript. Some advice: when things don't work right in Netscape, type javascript: in the url box. Netscape will display the Javascript console with any errors that occurred.<br> Secondly, Netscape's event handling is different from IE. In order to have a single handler that works in both Netscape and IE, I've found it easier to capture the events at the document or window level. In any case, with Netscape, you have to explicitly tell it to handle the event. This should get you started:<br><br>if (document.layers) <br>{<br> document.captureEvents(Event.KEYPRESS);<br>}<br>document.onkeypress=showMe;<br><br>function showMe(e) {<br> if (document.layers)<br> alert(e.target.name);<br> else<br> alert (event.srcElement.name);<br>}<br><br>If you do this, remove the onkeypress from the input tags<br><br>I'd suggest brushing up on the Netscape event handling model:<br><br><A HREF=" TARGET="_new"> <p>nick bulka<br><a href=mailto: > </a><br><a href= > </a><br>
- Thread starter
- #9
Nick, thanks for attempting to point me in the right direction. Whenever I type Javascript in the navigation window, it brings me to <A HREF=" TARGET="_new"> tells me nothing was found. What do you mean by the javascript console? I put the // in and changed the first input field to onKeyPress = handlePress(event,this). This is the routine I really am shooting for, I just put showMe()in for debugging purposes. With width = "640", it continues to ignore the onKeyPress. With width = "100%", I got the respective alerts OnMouseOver, before I enter any data the first time I accessed it. The next time it just ignored the code. I realize you probably have seen enough, but just in case you're interested the 100% variation is at
Rory,<br><br>you forgot the colon at the end<br><br>javascript:<br><br>you'll know what the javascript console is when you see it.<br>By the way, the results don't get cleared from the console window unless you explicitly clear them, even if you close the console and open it again.<br><br>Once you clear up your errors, if you still have problems, let us know. <br><br><br> <p>nick bulka<br><a href=mailto: > </a><br><a href= > </a><br>
- Thread starter
- #11
You'd think that after almost 20 years in this business I'd pay attention to things like colons but hey, maybe senility is setting in. The console isn't displaying any errors, so I guess it'll be trial and error to get the onKeyPress firing regularly. I'll let you know if I get it.
- Thread starter
- #12
I isolated the problem to a single table row which disables the onkeypress functionality in netscape. With this row, the routine does not fire. Without this row, the routines work correctly. I can see nothing functionally different in this row from the other 5, but it is the only row whose presence affects the execution of the code. I posted it at <A HREF=" TARGET="_new">
Rory dude, your cracking me up here, hehehehehe. Now this page :<br><br><A HREF=" TARGET="_new"> no 'showMe()' function, not to mention no <html> nor <body> tags. This has turned in to quite the adventure.<br><br>Ok so I took your code and produced this with it:<br>-----------------------------------------------------<br><html><br><head><br><SCRIPT ID=clientEventHandlersJS LANGUAGE=javascript><br><!--<br>function showMe(){<br><br> alert("showme"
;<br>}<br>//--><br></SCRIPT><br></HEAD><br><BODY><form><br><table border=1><br><tr><br><td height="36"><font <br> size="2">6. Maine Children's Trust Incorporated</font></td><br><td align=right > <br><input type="radio" name="kids" value="5" >$5 <br><input type="radio" name="kids" value="10">$10 <br><input type="radio" name="kids" value="25">$25 <br><input type="radio" name="kids" value="0" > Other </td><br><td align="right" <br> height="36"><font size="2">6</font> <input type="text"<br> name="AmtContrMEChild" size="12" <br> onKeyPress="showMe()"></td><br></tr></table><br></form><br></body><br></html><br>------------------------------------------------<br>And it works in IE4-5 and Nutscrap 4.06<br><br>Hope this helps<br>-pete
;<br>}<br>//--><br></SCRIPT><br></HEAD><br><BODY><form><br><table border=1><br><tr><br><td height="36"><font <br> size="2">6. Maine Children's Trust Incorporated</font></td><br><td align=right > <br><input type="radio" name="kids" value="5" >$5 <br><input type="radio" name="kids" value="10">$10 <br><input type="radio" name="kids" value="25">$25 <br><input type="radio" name="kids" value="0" > Other </td><br><td align="right" <br> height="36"><font size="2">6</font> <input type="text"<br> name="AmtContrMEChild" size="12" <br> onKeyPress="showMe()"></td><br></tr></table><br></form><br></body><br></html><br>------------------------------------------------<br>And it works in IE4-5 and Nutscrap 4.06<br><br>Hope this helps<br>-pete- Thread starter
- #14
Palbano, I thought I made it clear that the "problem" page contained only the line which seemed to cause the problem, not an entire functioning page. At any rate, further experimentation was done, & the end result seemed to indicate a limitation on how many form items Netscape could access successfully, based on the page structure. When I organize the array into 3 tables of two rows each, it works fine. Any other organization results in some of the input tags not firing "onKeyPress", though no errors are shown on the Javascript console. It would seem Netscape has a ways to go in providing a reliable programming platform with adequate diagnostics for troubleshooting.
Rory,<br> My experience is that you always have to fight with Netscape to get things to work to your satisfaction. Maybe this will change with Netscape 6, since it;s a total rewrite. <p>nick bulka<br><a href=mailto: > </a><br><a href= > </a><br>
event handlers in tables is not supported by Netscape. I have seen this same problem on other discussion boards. I know you can get event handlers to operate, usually inconsistently, in tables within Netscape. But I think this is more of a fluke than anything. Be assured that event handlers are not directly supported in Netscape.<br><br>Russ
P.S. NickBulka. You're right, Netscape 6.PR1 is available and does support a number of 'new' things that makes it easier to write for. It's available in Beta. I don't much like the appearance, but it sure is fast. Of course, Netscape has always been faster than IE on my system for some reason, but this is even faster.
Dear Rory,<br><br>>I thought I made it clear...<br><br>Yes, you are correct. Now that I can see the result, when I go back and read your previous posts it makes sense to me. I guess I just didn't get it. Sorry for the confusion, I'm glad you have it working now.<br><br>-pete
- Status
Similar threads
- Locked
- Question
- Locked
- Question
