64450 - invisible insertion point at google's advanced search

Status: VERIFIED DUPLICATE of bug 90756

(Core :: Layout: Form Controls, defect)

Description

[Jesse Ruderman]

1. Go to http://www.google.com/advanced_search.
2. Press a letter key.

Notice that the first textbox on the page has focus, but the insertion point
isn't visible.  In IE and Nav4, the textbox has focus and you can see the
insertion point.

Comment 1

[Jesse Ruderman]

Attachment: testcase

Comment 2

[Jesse Ruderman]

Hmm, ie doesn't give focus at all for that testcase.  (ns4 does, though.)

Comment 3

[rods (gone)]

reassigning

Comment 4

[rubydoo123]

handing over to jfrancis

Comment 5

[Joe Francis]

simon, sounds like event woes...

Comment 6

[Simon Fraser [no longer active]]

Over to anthonyd.

Comment 7

[anthonyd]

hmmm, this one is wierd.  Focus is definitely in the field, but why isn't the 
caret being drawn?  I will investigate this further, and will once again, cc 
Saari on this one.

anthonyd

Comment 8

[Vladimir Ermakov]

QA Contact Update

Comment 9

[anthonyd]

moving to mozilla 0.9.1

Comment 10

[Kathleen :Brade]

move to mozilla0.9.2

Comment 11

[rubydoo123]

this is still an issue using the build from 2001052020, the only way I can get 
the caret to render in the 1st textbox is to go to the next textbox and 
shift+tab back to it, clicking in the textbox doesn't do it, moving to 1.0

Comment 12

[Vladimir Ermakov]

For me the carret is invisible only the first time you click into the field. 
After you click on another field and click back I can see it. This is on build 
2001-05-22-06-trunk. Also in the testcase the table, which at first has some 
space under the text field shrinks once you start typing in the field.

Comment 13

[Jesse Ruderman]

> For me the carret is invisible only the first time you click into the field.

Since a script on the page does a textbox.focus(), you don't have to click in 
the field to reproduce this bug.  The insertion point is already in the field, 
and characters typed do go into the field.  (Note that the script that focuses 
the textbox is inline rather than onload.)

Comment 14

[Chase Tingley]

*** Bug 89378 has been marked as a duplicate of this bug. ***

Comment 15

[Madhur Bhatia]

this is still occuring on window2000 build - 20010719 

Comment 16

[saari (gone)]

in the attached testcase, if you move  </td></tr></table> back inside of the
<form></form> in a more proper nested fashion, it works. Neat.

Comment 17

[rubydoo123]

--> kin

Comment 18

[kinmoz]

--> mjudge (caret/selection)

Comment 19

[selmer (gone)]

Is this bug representative of a large class of sites that are broken?  If the
only place we see this is on that one page, then I question the EDITORBASE
nomination.  Perhaps a very small evangelism effort would fix the specific
problem on that page given what saari discovered.

Comment 20

[saari (gone)]

I'd think that only sites with improper tag nesting would be broken since the
syntactically correct html works fine. 

Comment 21

[Steve Bradshaw]

looks to me like it occurs on sites which use the javascript focus() method.

Comment 22

[saari (gone)]

no, there are many sites that use js focus just fine. It is something more
specific than that. As I noted, this case can be fixed by proper tag nesting.

Comment 23

[TucsonTester3]

Problem occurs on Mac OS 8.6, 9.0.4, 9.1, and X.  Using build id 2001112608.

Comment 24

[mjudge]

marking this future. this is a table embedding wierd tag case.  If this must be 
requalified give it to someone in tables.

Comment 25

[michael wendell]

Changing platform and OS to all / all per comment 23.

Comment 26

[Christopher Aillon (sabbatical, not receiving bugmail)]

*** Bug 120852 has been marked as a duplicate of this bug. ***

Comment 27

[R.K.Aa.]

*** Bug 130707 has been marked as a duplicate of this bug. ***

Comment 28

[Jesse Ruderman]

*** Bug 151524 has been marked as a duplicate of this bug. ***

Comment 29

[Niels Aufbau]

According to bug 51897 comment 14, this was fixed in bug 90756.

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

Comment 30

[Vladimir Ermakov]

verifying, it is fixed on 2002-07-01-08-trunk

Comment 31

[Serge Gautherie (:sgautherie)]

Acting on Duplicate resolution from bug 64450 comment 29:

*Moving 'Blocks: bug 64451' from bug 64450 to bug 90756.
 (Take further action as needed.)