Bug 93747 - [testcase] call of javascript.focus does change focus, but didn't set cursor
Summary: [testcase] call of javascript.focus does change focus, but didn't set cursor
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml forms (show other bugs)
Version: 3.3.1
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 123388 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-22 21:44 UTC by newsscott
Modified: 2012-06-18 14:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Testcase in description (548 bytes, text/html)
2008-04-06 13:03 UTC, kirun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description newsscott 2004-11-22 21:44:27 UTC
Version:           3.3.1 (using KDE KDE 3.3.1)
Installed from:    Debian testing/unstable Packages
OS:                Linux

the following code sets the focus on the input field. You can enter some text, but the cursor isn't shown. It only will appear, if you trigger a focus again (key or mouse) or if you enter some text which is known by that 'auto-fill' combobox. If you remove the <link> tag, everthing is ok. It is not important, if that css exists or not:

<HTML>
  <HEAD>
    <LINK href="xyz.css" type="text/css" rel="STYLESHEET">
  </HEAD>

  <BODY>
    <FORM name="userForm" method="post" action="" id="userForm">
      <INPUT type="text" name="username" maxlength="16">
    </FORM>
    <SCRIPT type="text/javascript" language="JavaScript">
        var focusControl = document.forms["userForm"].elements["username"];
        
        if (focusControl.type != "hidden" && !focusControl.disabled) {
        focusControl.focus();
        }
    </SCRIPT>
  </BODY>
</HTML>
Comment 1 Stephan Kulow 2004-11-23 11:53:47 UTC
we got some issues with forms, focus and cursors
Comment 2 miro 2005-02-06 12:34:45 UTC
After element.focus I get 2 cursors sometimes!
Comment 3 miro 2005-02-06 12:42:26 UTC
When moving an element in the mouseOver handler, so that the mouse is no longer
"Over" it no mouseOut is fired!
Comment 4 Maksim Orlovich 2005-11-04 07:26:25 UTC
yeah, that'd be because it doesn't even try. However, I am not entirely clear on what it should do -- what if the JS is running in a tab that's hidden, etc?
Comment 5 Maksim Orlovich 2006-10-28 20:04:01 UTC
*** Bug 123388 has been marked as a duplicate of this bug. ***
Comment 6 kirun 2008-04-06 13:03:28 UTC
Created attachment 24234 [details]
Testcase in description
Comment 7 Māris Nartišs 2010-01-15 09:19:51 UTC
I'm unable to reproduce missing cursor in input field with 4.3.4. Still JS focus function causes double blinking cursor, as described by miro (load test case, JS gives focus to input field, click in address bar or search tool - input still has bouncing cursor). IMHO double blinking cursor should have own bug (I could not find already existing bug with such description).
Comment 8 Myriam Schweingruber 2012-06-18 14:12:42 UTC
Message from the Bugsquad and Konqueror teams:
This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore.
If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report.
Thank you for your understanding.