Closed Bug 75746 Opened 24 years ago Closed 1 year ago

Need to press down-arrow key twice to go to next item in list (after adding style)

Categories

(SeaMonkey :: Composer, enhancement, P5)

x86
Windows NT
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: shrir, Unassigned)

Details

(Keywords: topembed+, Whiteboard: [NC][caret][navigation] EDITORBASE+,edt_x3,edt_b3,edt_c3)

windows trunk 0411 steps: 1 Launch composer 2 Create a bullet list with 3-4 items 3 Using keyboard, place the caret after the last character of,say, the 2nd item 4 Now do a SHIFT + HOME to highlight the list item and then do a CTRL + B 5 Observe that the 'bold' style gets applied and the list item remains highlighted and the caret keeps blinking at the end of the last character in the list (which is all normal) 6 Press the down-arrow key once expecting the caret to go to the next list item 7 Observe that the caret stays on the same list item and the highlight goes away expected: when i click down-arrow once, highlight should go away and the caret should go to the next list item. I have to press the button twice to go to the next item. Should behave as in 4.x
Reassigning to anthonyd.
Assignee: kin → anthonyd
note: on Macintosh, the down arrow should move to the end of a selection (if it's not already collapsed); an up arrow with a selection should move the caret to the beginning of the selection. Is the requested behavior particular to Windows and the selection with a blinking caret or ???
Given more important caret issues, this doesn't seem very critical to me!
Move to mozilla.0.9.1 for now.
Target Milestone: --- → mozilla0.9.1
Move this to mozilla1.0; anyone should feel free to help Tony out with this bug (unless he resets the milestone).
Target Milestone: mozilla0.9.1 → mozilla1.0
Status: NEW → ASSIGNED
Whiteboard: [caret][navigation]
this is specific behaviour for windows, and is very, very non-critical. -->mjudge for caret/selection bugs
Whiteboard: [caret][navigation] → [NC][caret][navigation]
--> kin
Assignee: anthonyd → kin
Status: ASSIGNED → NEW
--> mjudge (selection navigation)
Assignee: kin → mjudge
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
confirmed but soooo minor
Severity: normal → minor
Priority: -- → P5
Target Milestone: mozilla1.0.1 → Future
Whiteboard: [NC][caret][navigation] → [NC][caret][navigation] EDITORBASE
Keywords: topembed
Discussed in edt. Plussing.
Keywords: topembedtopembed+
Whiteboard: [NC][caret][navigation] EDITORBASE → [NC][caret][navigation] EDITORBASE,edt_x3,edt_b3,edt_c3
This behaves how I'd want it to behave (as a MacOSX user?). I think this bug is invalid. Michael Buckland--can you clarify the behavior you expect and whether that behavior is Windows-specific? Feel free to cc me on any other related bugs if there is discussion elsewhere. remove topembed+ and seek retriage.
Keywords: topembed+topembed
plussing again. MS Word on windows is the behavior we're after here. This bug should be for windows only if mac behavior is different we should consider platform specific behavior if possible. If not possible, MS Word on windows is our guide in the name of "polish" in this area.
Keywords: topembedtopembed+
EDITORBASE+
Whiteboard: [NC][caret][navigation] EDITORBASE,edt_x3,edt_b3,edt_c3 → [NC][caret][navigation] EDITORBASE+,edt_x3,edt_b3,edt_c3
Can we have updated milestone? When might a fix land?
ok windows only "bug".
Status: NEW → ASSIGNED
Summary: Need to press down-arrow key twice to go to next item in list (after adding style) → [rfe]Need to press down-arrow key twice to go to next item in list (after adding style)
Target Milestone: Future → mozilla1.7alpha
[RFE] is deprecated in favor of severity: enhancement.
Severity: minor → enhancement
Summary: [rfe]Need to press down-arrow key twice to go to next item in list (after adding style) → Need to press down-arrow key twice to go to next item in list (after adding style)
QA Contact: sujay → editor
Assignee: mjudge → nobody
Status: ASSIGNED → NEW
Severity: normal → S3

Verified this was fixed in SeaMonkey 2.53.18.1

Status: NEW → RESOLVED
Closed: 1 year ago
Component: DOM: Editor → Composer
Product: Core → SeaMonkey
Resolution: --- → FIXED
Target Milestone: mozilla1.7alpha → ---
You need to log in before you can comment on or make changes to this bug.