Closed Bug 127321 Opened 23 years ago Closed 23 years ago

option-right-arrow moving between words stops at punctuation

Categories

(Core :: DOM: Editor, defect, P1)

PowerPC
All
defect

Tracking

()

VERIFIED FIXED
mozilla1.0

People

(Reporter: chris, Assigned: mjudge)

References

Details

(Keywords: platform-parity, regression, topembed+, Whiteboard: EDITORBASE+)

Attachments

(1 file, 1 obsolete file)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.8) Gecko/20020204 BuildID: 2002020405 if you use option-right-arrow to move from word to word in the compose window (HTML compose) you get 'stuck' at punctuation marks. The cursor won't go any further. using option-left-arrow seems to work ok. Reproducible: Always Steps to Reproduce: 1.compose and HTML mail 2.use option--right-arrow to move around 3.
over to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Product: MailNews → Browser
QA Contact: sheelar → sujay
--> mjudge (selection/caret navigation)
Assignee: kin → mjudge
This may be affected by a pref introduced by pinkerton (so it may not appear on Windows?). Pink--Mike will probably need to know the pref; do you know what it is?
Keywords: pp
i think one of the prefs is layout.word_select.stop_at_punctuation but it should be pretty easy to find them in the code.
I'll add that this also occurs in text boxes in Navigator (such as the one I'm typing in now ...). Also, the cursor gets stuck on every non-alphnumeric character I've thrown at it (parentheses, plus sign, dash, period, etc.). I'm using build 2002032808.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: nsbeta1, topembed
*** Bug 137754 has been marked as a duplicate of this bug. ***
Severity: critical → normal
OS: Mac System 9.x → All
Whiteboard: EDITORBASE
basic keyboard accessiblity. can't ship w/out this fixed.
Severity: normal → critical
Target Milestone: --- → mozilla1.0
I didn't even know you could do that in any editor... so I'm not sure I agree with the basic functionality assessment. If it is a regression I'm inclined to make it EDITORBASE+ however.
Keywords: topembedtopembed-
hello? every text field on macos has done that since 1984.
<shrug> Okay. Is it a regression for us?
Yes, this is a regression; the regression keyword is already defined in the keywords section.
editorbase triage: EDITORBASE-. leaving topembed+
Whiteboard: EDITORBASE → EDITORBASE-
Kevin, this is a regression and a lot of people are noticing it. Are we sure this is a minus?
Priority: -- → P1
*** Bug 141909 has been marked as a duplicate of this bug. ***
*** Bug 148374 has been marked as a duplicate of this bug. ***
seeking reconsideration on this; it's very wrong and should be fixed
Whiteboard: EDITORBASE- → EDITORBASE
EDITORBASE+
Whiteboard: EDITORBASE → EDITORBASE+
is this not bug 108125?
ok the WRONG part is that you get STUCK on the punctuation? I mean you cant advance any further by word jumping when you hit a punctuation or that you shouldnt even stop at the punctuation at all. I just need some hints.
Status: NEW → ASSIGNED
Mike--the problem is that you can't continue moving the caret with that keybinding. Once I hit that punctuation, I expect to be able to continue to option-right-arrow to get to the next word.
this looks good to me. and in a good place. if we are on punctuation, keep reading in punctuation. if we are on alpha numerics keep reading until we hit punctuation.
Comment on attachment 94245 [details] [diff] [review] ok this fixes skipping of multiple punctuation. can the local variable "readingAlNum" be changed to something more readable such as "readingAlphaNumeric" or even better: "isReadingAlphaNumeric"? Does this work with non-latin1 charset?
changed readAlNum to readingAlphaNumeric. the function that is changing is: ScanNormalAsciiText_F_ForWordBreak which is not used by anything non ASCII.
Attachment #94245 - Attachment is obsolete: true
Comment on attachment 94362 [details] [diff] [review] dif to fix skipping multiple punctuation. with new varname r=brade
Attachment #94362 - Flags: review+
Different editors behave differently w.r.t punctuation, and spaces. The current patch treats runs of punctuation as 'words' and jumps them in 1 go. BBEdit on OS 9 goes 1 char at a time through punctuation; TextEdit on X skips runs of punctuation. Some editors will skip single/multiple punc chars at the start of a word. Do we care?
Comment on attachment 94362 [details] [diff] [review] dif to fix skipping multiple punctuation. with new varname sr=sfraser
Attachment #94362 - Flags: superreview+
*** Bug 108125 has been marked as a duplicate of this bug. ***
checked into trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
I migrated this fix to the CHIMERA_M1_0_1_BRANCH too.
*** Bug 175387 has been marked as a duplicate of this bug. ***
vrfy'd fixed with 2003.02.19 (behavior the same on mac 10.2.4 and linux rh8.0).
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: