Closed Bug 29570 Opened 25 years ago Closed 24 years ago

Mac doesn't retain caret x-coord

Categories

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

PowerPC
Mac System 8.5
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: elig, Assigned: mjudge)

Details

(Whiteboard: [nsbeta3+]FIX IN HAND)

* TITLE/SUMMARY Mac doesn't retain caret x-coord (writing up as convenience to mjudge) * STEPS TO REPRODUCE 0) Launch Apprunner 1) From the Debug menu, select "Composer with Test Page" 2) Click between the "h" and "m" in the boldfaced "html" (second sentence) 3) Press the arrow key downwards a few times. * RESULT - What happened The caret won't retain the same x-coordinate, but will default to the left-hand column of text. (Normally.) - What was expected Caret should retain same x-coord while moving downwards. * REGRESSION - Occurs On Mac OS Apprunner (2000022808 AM optimized build) - Doesn't Occur On Win32 Apprunner (2000022808 optimized build [NT 4, Service Pack 5]) Linux Apprunner ("1999122808" [aka this morning's] optimized build) * CONFIGURATIONS TESTED - [Mac] Beige Power Mac G3 (266 MHz PowerPC 750), 96 MB RAM (VM on; 1 MB of VM used), 1024x768 (Thousands of Colors), Mac OS 8.6 - [Win32] Vectra VL (233 MHz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP5. - [Linux] Vectra VL (266 MHz P2), 96 MB RAM. Red Hat Linux 6.0 (GNOME).
Eli or Sujay--any ideas when this broke?
Keywords: pp
Priority: P3 → P2
Target Milestone: M15
Sorry --- didn't know it ever worked. ;)
Keywords: relnote
moving to M16
Target Milestone: M15 → M16
Per Beth, we're moving this out to M18.
Target Milestone: M16 → M18
something to do with the way the mac drag select out of a single line text field must select to beginning or end. I think this may have caused this regression.
Status: NEW → ASSIGNED
Keywords: pp, relnotecorrectness, nsbeta3
setting to nsbeta3+
Whiteboard: nsbeta3+
adding the brackets in the status
Whiteboard: nsbeta3+ → [nsbeta3+]
fix in hand. rdy to go.
changing whiteboard
Whiteboard: [nsbeta3+] → [nsbeta3+]FIX IN HAND
fixed
forgot to mark fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified in 8/11 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.