344715 - text selection is increasingly off as I progress to the right of the field

Status: VERIFIED WORKSFORME

(Camino Graveyard :: General, defect)

Description

[David Grokit]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1a3) Gecko/20060614 Camino/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1a3) Gecko/20060614 Camino/1.0+

I cannot give out the page I created this on because it is private, but any field does this.  In OS X 2.4.8 the selection of text is very difficult because it does not select directly below the cursor as in the following example. I typed this line of 00xx11xx00 repeatedly across the field and then went back over and clicked between the 1's and typed in an 8 which was only placed correctly on the left side of the field. Each additional click to the right placed the 8 a digit or more to the right.  This inability to edit text keeps me from using Camino at all.  All versions so far have done this.  The last click and insert placed the 8, 5 spaces to the right of the double 11's.

00xx181xx0000xx118xx0000xx11x8x0000xx11x8x0000xx11xx80000xx11xx80000xx11xx08000xx11xx00800xx11xx00800xx

Reproducible: Always

Comment 1

[Chris Lawson (gone)]

This may well be a dupe of bug 288047.

What the heck is "OS X 2.4.8" ?

cl

Comment 2

[froodian (Ian Leue)]

I don't quite understand the behavior you're describing.  Could you give step-by-step instructions for reproducing?

Comment 3

[David Grokit]

My apologies for my brain cloud, my OS is 10.2.8.   I was trying to show that when I try to edit text that has already been typed, it is not possible to select the text under the cursor.  As you move across the page to the right in a text field the selection increasingly moves to the right of the cursor.  I tried to show this by typing a repeating string of 00xx11xx00 and then going back in to try and select by clicking the mouse on the space between the two ones to insert an 8.  On the left hand side of the text field, when I typed an 8 it was placed correctly, but it gets progressively worse as you move to the right, as is indicated by the placement of the 8's in this text string.  All 8's should have inserted between the two ones, but on the right they are 5 spaces off.  This occurrs in the this text field as well.  Please note: the first 8 is correct, the second is one space to the right of the ones, the third is two spaces to the right, the forth is also two, but the fifth and sixth are three spaces off, the seventh 8 is 4 spaces off and the eighth and ninth are 5 spaces off.  They should all look like 00xx181xx00, but the last one to the right looks like this 00xx11xx008 instead.

00xx181xx0000xx118xx0000xx11x8x0000xx11x8x0000xx11xx80000xx11xx80000xx11xx08000xx11xx00800xx11xx00800xx

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

David, what font are you using for the fixed-width font?

Torben, can you repro this on your 10.2.8 machine?

Comment 5

[Torben]

> Torben, can you repro this on your 10.2.8 machine?

No, I can't reproduce this but i'm not sure I understand what David is doing...

> typing a repeating string of 00xx11xx00 

All on one line with no spaces in between?

> select by clicking the mouse [...] as you move to the right

How do you move? using the mouse, the arrow key, or something else?

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

David, could you please respond to the questions in comment 5?

Also, do you have any Windows Media content open when this happens?

Comment 7

[David Grokit]

I am just moving my mouse over the text and clicking to select between the two 1's and trying then to type an 8 at that location, but the location that the typed 8 appears in is not between the two 1's but appears off to the right of the 1's and the farther to the right in the field I am selecting, the farther off the * appears.

Comment 8

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Camino 1.0+ (nightlies) does not support Mac OS X 10.2.8 any longer, so even if someone else could reproduce this bug on 10.2, it would not be fixed.