PHP IDE :: NuSphere Forums :: View topic

Posted: Wed Mar 15, 2006 10:03 am

I have many scripts, where a javascript puts focus on an input field just after the onload of the window. It works perfectly in any external browser, but not in the IDE's browser (Output tab).

Posted: Wed Mar 15, 2006 12:12 pm

Probably, it's because when that JScript works, the output window is not active.

Posted: Wed Mar 15, 2006 4:32 pm

I think it's something related with the debugging process. If I just "run" (Ctrl-F9) the script, the field gets focus correctly. But if I "run in debugger" (F9), the field receives focus for a while (1-2 cursor blinks) and looses it. It doesn't matter if I'm using Adaptive Gui or not. It seems that the debug windows (Locals, Globals, etc) "steel" the focus just after page has finished loading.

Posted: Tue Mar 28, 2006 7:14 am

Any news about this issue?

Posted: Wed Mar 29, 2006 4:09 am

Quote:

If I just "run" (Ctrl-F9) the script, the field gets focus correctly

Does it retain focus if you switch to another tab and return back?

Posted: Wed Mar 29, 2006 5:44 am

ddmitrie wrote:

Does it retain focus if you switch to another tab and return back?

No, it does not.

Posted: Wed Mar 29, 2006 9:20 am

Please submit a short HTML+php file that will replicate this problem.

Posted: Thu Mar 30, 2006 12:20 am

Here it is:

Code:

//test.php
<html>
<head>
<script type='text/javascript'>
window.onload = function(){
document.getElementById('user').focus();
};
</script>
</head>
<body>
<form method='post' action='#'>
<fieldset style='width:1%'>
<legend class='cor'>Authentication</legend>
<table class='cor' align='center' style='width:300px'>
<tr><td class='tdbold' style='text-align:right'>User:</td>
<td><input type='text' name='user' id='user' value=''></td></tr>
<tr><td class='tdbold' style='text-align:right'>Password:</td>
<td><input type='password' name='pass' id='pass' value=''></td></tr>
<tr><td colspan='2' align='center'><hr>
<input type='submit' value='Login'></td>
</tr>
</table>
</fieldset>
</form>
</body>
</html>

Posted: Wed Apr 12, 2006 11:41 am

No news about? Could you replicate the problem?

Posted: Wed Apr 12, 2006 6:15 pm

we fixed this problem in v4.5.

Posted: Thu Apr 13, 2006 11:29 am

Version 4.5 requires upgrade ($$), shouldn't the 4.01 be rebuilt with the fix?

Posted: Fri Apr 14, 2006 10:04 am

Not actually. We fixed some components and if we put them into 4.0, it would require a) some development b) new tests. As a result this minor fix (from the user perpectives) causes sensible changes in the code.
If $$ is the only reason not to upgrade, please contact our sales dept. for the offer. As I understand, they can offer you either good discount or next upgrade for free.