Closed Bug 5787 Opened 26 years ago Closed 25 years ago

In editor, scrolling doc displays duplicate I beam carets when typing

Categories

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

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: chrispetersen, Assigned: sfraser_bugs)

References

Details

Version: Apprunner Build: April 29th Build (1999042908) Platform: All Expected Results:After scrolling the document, only one I beam cursor should be displayed. What I got: When typing after scrolling the document, two I beam cursors are displayed. Steps to reproduce: 1) Launch Apprunner. 2) From the Tasks menu, select the Editor menu. 3) Partially scroll the document 4) Now, click in the document as start typing. Notice two I baem cursors are displayed.
Assignee: kostello → sfraser
Target Milestone: M6
Reassigning to Simon Fraser, setting milestone to M6
Target Milestone: M6 → M7
Status: NEW → ASSIGNED
Minor cosmetic thing. M7.
*** Bug 6687 has been marked as a duplicate of this bug. ***
*** Bug 5977 has been marked as a duplicate of this bug. ***
QA Contact: 4079 → 4144
assigning qa_contact to Chris Petersen
Summary: In editor, scrolling the document displays dupilcate I beam cursors when typing.. → In editor, scrolling doc displays duplicate I beam cursors when typing
Target Milestone: M7 → M9
move to M9 per 6/15/99 meeting
Summary: In editor, scrolling doc displays duplicate I beam cursors when typing → In editor, scrolling doc displays duplicate I beam carets when typing
fix summary
Target Milestone: M9 → M10
Cosmetic. M10. The problem happens when we get a refresh on updating the window; I get passed a rendering context that has a different coordinate system. Not quite sure how to fix this yet.
Target Milestone: M10 → M11
M11
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Caret fixes checked in. Please reopen if you continue to see problems.
Status: RESOLVED → VERIFIED
With the Sept 16th build, this problem appears to be fixed.
You need to log in before you can comment on or make changes to this bug.