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)
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)
1.13 KB,
patch
|
Brade
:
review+
sfraser_bugs
:
superreview+
|
Details | Diff | Splinter Review |
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.
Comment 1•23 years ago
|
||
over to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Product: MailNews → Browser
QA Contact: sheelar → sujay
Comment 3•23 years ago
|
||
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
Comment 4•23 years ago
|
||
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.
Comment 5•23 years ago
|
||
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.
Updated•23 years ago
|
Comment 6•23 years ago
|
||
*** Bug 137754 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
Severity: critical → normal
OS: Mac System 9.x → All
Whiteboard: EDITORBASE
Comment 7•23 years ago
|
||
basic keyboard accessiblity. can't ship w/out this fixed.
Severity: normal → critical
Updated•23 years ago
|
Target Milestone: --- → mozilla1.0
Comment 8•23 years ago
|
||
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.
Updated•23 years ago
|
Comment 9•23 years ago
|
||
hello? every text field on macos has done that since 1984.
Updated•23 years ago
|
Comment 10•23 years ago
|
||
<shrug> Okay. Is it a regression for us?
Comment 11•23 years ago
|
||
Yes, this is a regression; the regression keyword is already defined in the
keywords section.
Comment 12•23 years ago
|
||
editorbase triage: EDITORBASE-. leaving topembed+
Whiteboard: EDITORBASE → EDITORBASE-
Comment 13•23 years ago
|
||
Kevin, this is a regression and a lot of people are noticing it. Are we sure
this is a minus?
Updated•23 years ago
|
Priority: -- → P1
Assignee | ||
Comment 14•23 years ago
|
||
*** Bug 141909 has been marked as a duplicate of this bug. ***
Comment 15•23 years ago
|
||
*** Bug 148374 has been marked as a duplicate of this bug. ***
Comment 16•23 years ago
|
||
seeking reconsideration on this; it's very wrong and should be fixed
Whiteboard: EDITORBASE- → EDITORBASE
Comment 18•23 years ago
|
||
is this not bug 108125?
Assignee | ||
Comment 19•23 years ago
|
||
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
Comment 20•23 years ago
|
||
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.
Assignee | ||
Comment 21•23 years ago
|
||
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 22•23 years ago
|
||
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?
Assignee | ||
Comment 23•23 years ago
|
||
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 24•23 years ago
|
||
Comment on attachment 94362 [details] [diff] [review]
dif to fix skipping multiple punctuation. with new varname
r=brade
Attachment #94362 -
Flags: review+
Comment 25•23 years ago
|
||
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 26•23 years ago
|
||
Comment on attachment 94362 [details] [diff] [review]
dif to fix skipping multiple punctuation. with new varname
sr=sfraser
Attachment #94362 -
Flags: superreview+
Comment 27•23 years ago
|
||
*** Bug 108125 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 28•23 years ago
|
||
checked into trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 29•22 years ago
|
||
I migrated this fix to the CHIMERA_M1_0_1_BRANCH too.
Comment 30•22 years ago
|
||
*** Bug 175387 has been marked as a duplicate of this bug. ***
Comment 31•22 years ago
|
||
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.
Description
•