Open Bug 244517 Opened 21 years ago Updated 2 years ago

in address list, forward and back arrow keys don't move between addresses

Categories

(MailNews Core :: Composition, enhancement)

x86
Windows XP
enhancement

Tracking

(Not tracked)

People

(Reporter: danielbarclay.oss, Unassigned)

References

(Depends on 1 open bug)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421 In the address text box list, when the text insertion point is at the end of the text in one address, the forward arrow key does not move to the beginning of the next address. Similarly, when back arrow key does not move to the end of the previous address when the text insertion point is at the beginning of an address. (Recall how the Backspace key moves from an address box being deleted to the end of the previous address.) Reproducible: Sometimes Steps to Reproduce: 1. Click at the end of an address in the list. 2. Press the forward arrow key. 3. Click at the beginning of an address in the list. 4. Press the back arrow key. Actual Results: Nothing for steps 2 and 4. Expected Results: In step two, Mozilla should have placed the text insertion point at the beginning of the next address. In step four, Mozilla should have placed the text insertion point at the end of the previous address.
I don't think this behavior was ever intended; in fact, I'm not even sure it's desirable. Bug 244512 is a much better candidate to be fixed.
Severity: normal → enhancement
Depends on: 244512
> I don't think this behavior was ever intended; in fact, I'm not even sure it's > desirable. Bug 244512 is a much better candidate to be fixed. Backspace (mostly) works as if the address boxes are multiple lines of text, moving from one box to another after deleting characters in a later box. Other keys should work similarly. In text, the forward arrow key moves between characters and then moves from the end of one line to the beginning of the next (traversing over the space, line break, or paragraph break dividing the lines). In the address line, the forward arrow key moves between characters. Why shouldn't it also move from the end of one address to the beginning of the next (traversing over whatever is considered to divide one from the next). I think the real bug is at a higher level: The design has no consistent model for how the list of address text boxes should work as a unit.
Product: MailNews → Core
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/
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: 19 years ago
Resolution: --- → EXPIRED
This bug (or, possibly, non-bug) still exists in Mozilla 1.7.12. What did arrow keys do in Netscape 4.x? Didn't Backspace and Delete at the beginning and end, respectively, of an address box treat the boundary between addresses (address boxes) the same way editors treat line breaks (deleting blank entries or lines, or joining two entries or lines into one)? It seems that arrow keys should similarly treat boundaries as entities that can be stepped over (as if the list of address boxes were just a fancier rendering of a list of lines).
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
(In reply to comment #5) > This bug (or, possibly, non-bug) still exists in Mozilla 1.7.12. In this case, it doesn't matter, but Seamonkey 1.0a is the minimum version against which you should be reporting bugs; 1.7.x is old news. > What did arrow keys do in Netscape 4.x? Didn't Backspace and Delete at > the beginning and end, respectively, of an address box treat the boundary > between addresses (address boxes) the same way editors treat line breaks > (deleting blank entries or lines, or joining two entries or lines into one)? > > It seems that arrow keys should similarly treat boundaries as entities that > can be stepped over (as if the list of address boxes were just a fancier > rendering of a list of lines). Personally, I disagree; I think the up/down arrows should (consistently) move between the fields, but the right/left should be limited to the current field. There is, in fact, an RFE to prevent backspace/delete from crossing field boundaries: bug 170292. I'll confirm this bug only because it's arguably a valid position, but if someone is going to go the effort to figure out to fix this, they should focus on bug 244512 *first*.
> In this case, it doesn't matter, but Seamonkey 1.0a is the > minimum version against which you should be reporting bugs; > 1.7.x is old news. What do you mean Mozilla 1.7.x is old news? (Since when? 1.7.12 was released within the last couple months, right? In fact, I just upgraded from 1.7.11 to 1.7.12 to have the latest version of Mozilla before I commented on this bug.) Also, what the heck is Seamonkey? I know of Mozilla (Suite), Firefox, and Thunderbird. What exactly is Seamonkey (1.0a) a codename for? You need need to end-user-visible names of products (or at least names like "Gecko" that show up when the end user invokes the About Mozilla command) when telling end users what's supported. Are you trying to say that Mozilla Suite isn't being supported at all?
Really confirming this now.
Status: UNCONFIRMED → NEW
Ever confirmed: true
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
QA Contact: composition
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.