White space doesn't seem to be defined right

RESOLVED WORKSFORME

Status

SeaMonkey
Composer
RESOLVED WORKSFORME
15 years ago
13 years ago

People

(Reporter: Frank Spade, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827

When I double-click at the first underscores in the following string, the whole
string including the comma at the end is selected. I would expect the selection
to stop at the blank after the first line of underscores. When I double-click at
"at" the remaining characters including the comma at the end is selected.

___________ at ________ ,

Testing this even in this texarea input box I am using right now produces more
desirable results.

Reproducible: Always

Steps to Reproduce:
1. Copy the string "___________ at ________ ," into composer
2. double-click at any part of it and see the resulting selection
3. goto preview and repeat 2.
4. save page and load in Mozilla, repeat 2.

Actual Results:  
The whole string or the remaining string including the comma at the end is selected.

Expected Results:  
The selection should stop with the first white-space not with the first
non-white-space character. 
If the selection consists of white-space characters it should stop with the
first white-space character that is different than the one clicked at.

Comment 1

15 years ago
--> Composer
Assignee: general → composer
Component: Browser-General → Editor: Composer
QA Contact: general → petersen
Product: Browser → Seamonkey
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 3

13 years ago
I get the expected results when I try the steps to reproduce. Seamonkey 1.1a rv:
1.9a1 build 2005100105 under XP Pro SP2 here.

Resolving as WORKSFORME

Reporter, if the problem still persists with a recent nightly trunk build, then
reopen the bugfile.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.