Closed
Bug 268092
Opened 21 years ago
Closed 20 years ago
spaces mess up cursor position in location bar after 10.3.6 upgrade
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: mike, Unassigned)
Details
Attachments
(1 file)
298.24 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910
This issue is new after loading the 10.3.6 upgrade. When typing in the location
bar, spaces make the insertion cursor move slightly to the right. Typing more
and more spaces (as when doing a search) make the cursor position track farther
and farther to the right. Form text fields are also affected but not as
dramatically as is the menu bar. In a text field, the incorrect position is
reset after reaching the end of a line. Stray characters can appear at the end
of the line, though when the beginning of a word appears on that line.
Reproducible: Always
Steps to Reproduce:
1. Upgrade to 10.3.6.
2. Type in menu bar or text field using spaces.
Actual Results:
Cursor advances past actual insertion postion.
Expected Results:
Cursor tracks with insertion position
Reporter | ||
Comment 1•21 years ago
|
||
The attached screen shot shows the cursor position being off. Also, towards the
right side of the picture there is left over text and highlighting (in pink)
from the URL in the location bar before typing the search text.
Reporter | ||
Comment 2•21 years ago
|
||
It seems that the OS hadn't fully loaded its fonts or something before I
launched Mozilla. After quitting Mozilla and re-launching the app, things
returned back to normal. I don't know if this should still stay as a bug to
better deal with a no fonts situation, but luckily it's not truly related to 10.3.6.
Severity: minor → trivial
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 3•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•