[Webkit-unassigned] [Bug 12562] Fix test cases that are now spewing console errors that they are not testing for

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=12562





------- Comment #4 from sam at webkit.org  2007-02-04 07:54 PDT -------
(In reply to comment #3)
> (In reply to comment #2)
> > (From update of attachment 12903 [edit] [edit])

> > +caret: position 1 of child 0 {INPUT} of child 0 {DIV} of child 0 {BODY} of
> > child 0 {HTML} of document
> > 
> >    If the caret is inside the <input>, won't it have a focus ring (which is
> > what this test says shouldn't happen)?
> 
> I'm not exactly sure what is happening here (I need to investigate it further)
> but this is not clicking inside the <input>.  If it was, with a
> eventSender.mouseMoveTo(100, 45) like its sister test
> input-text-click-inside.html, the png would show focus ring.  As I said I'm not
> exactly sure what the caret: ... syntax means in this case.

I talked to mitz on IRC about this and he says this is the correct behavior. 
This indicates that the caret is not inside the input, which the png also
shows.

> > -caret: position 9 of child 0 {#text} of child 7 {DIV} of child 7 {DIV} of
> > child 1 {BODY} of child 0 {HTML} of document
> > +selection start: position 9 of child 0 {#text} of child 3 {DIV} of child 7
> > {DIV} of child 1 {BODY} of child 0 {HTML} of document
> > +selection end:   position 0 of child 5 {DIV} of child 7 {DIV} of child 1
> > {BODY} of child 0 {HTML} of document
> > 
> >    Why are we ending up with a selection now?
> > 
> 
> We are selecting the third table element.  At first I thought that was correct,
> but now I can't see why.  Will look into it further as well.
> 

I am changing this so that we no longer have a selection by increasing the
leapForward time to 1000ms.

New patch forthcoming.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.