When calling textfield.focus(), I would expect the caret to become visible, be it at the end, or at the beginning of the textfield contents. What happens now is that the textfield does get focus, but the caret is places at an invisible position.(At the end of the text). This can be seen my giving the textfield a maximum width, and filling it with a long string. Then call focus(), and see : no caret.

When loading the testcase, hold "LEFT ARROW" to let the cares scroll into view. This demonstrates that the textfield has acquired focus.

Also seen on Linux, changing to All/All

*** This bug has been marked as a duplicate of 48400 ***

Verified dupe of ->M19 bug 48400: "Using textfield.select() with empty contents doesn't show caret (collapsed selection)"

This bug has been marked duplicate, and the one is has been marked dupe of has been fixed. A number of related bugs have also been fixed, but it seems that this still does not work in a simple HTML page. The testcase will call focus() on a textfield after the page has been loaded, but alas: no caret appears. It seems to me this bug is the best candidate to reopen.

reassigning to brade - not a sizing issue.

sounds like a focus issue... -->saari

brade, the focus is there, but the text entry field isn't "scrolling" to show the caret. That is an ender thing.

Moving to Mozilla1.1

2002042008 OS/2 trunk Doesn't anyone use Google advanced groups search? http://www.google.com/advanced_group_search?hl=en Every time I execute back to this page after a previous search failed to turn up needed results, there is no apparent focus anywhere. I click in the first box (with all the words), and no cursor shows up. Only after clicking in another input field does the cursor appear anywhere.

Still seeing this with Mozilla 1.0 RC1

Ditto here with RC1. In addition to the scenario reported by mrmazda@atlantic.net, I find that even a 1st loading of http://www.google.com/advanced_group_search?hl=en produces no cursor in the "with all the words" input field. The cursor would only appear if I use the mouse to click in ANY one of the other input field.

FYI, the problem seen at http://www.google.com/advanced_group_search?hl=en is totally different from the original reported problem. The google problem was due to the fact that the textwidget was given focus and then DemoteForm() destroyed and recreated the frame tree so the caret was never turned back on for the new textwidget frame. The google problem should be fixed on the TRUNK with the removal of DemoteForm() (bug 90756)

nsbeta1-. More severe issue in this bug is fixed by patch for bug 90756.

Still present in mozilla 1.1 alpha.

Are you sure you want to future this one? A textfield that doesn't show any indication of being active when in actually should seems a pretty stupid usability flaw.

*** This bug has been marked as a duplicate of 64170 ***