Closed Bug 141888 Opened 23 years ago Closed 23 years ago

Caret not displayed in composer with pages containing readonly or disabled text widgets

Categories

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

x86
Other
defect

Tracking

()

VERIFIED FIXED
mozilla1.1beta

People

(Reporter: schellong, Assigned: mjudge)

References

()

Details

(Keywords: regression, Whiteboard: EDITORBASE)

Attachments

(2 files, 3 obsolete files)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; OpenUNIX i386; en-US; rv:1.0rc1) Gecko/20020419 BuildID: 2002041915 http://www.schellong.de/index.htm --> Edit Page --> in Composer the text cursor is invisible at all. Reproducible: Always Steps to Reproduce: 1. Load Page 2. Edit Page 3. Place the -invisible- Cursor Actual Results: Text cursor is invisible Expected Results: Text cursor is always visible
confirming....
Status: UNCONFIRMED → NEW
Ever confirmed: true
I can confirm this. I am experiencing this problem as well. Sometimes the cursor is restored, but then it disappears again once I start clicking on areas or click on another tab, like the Source tab or something. Not sure if that is what triggers it, but it makes it real hard to use the editor since you don't know for sure where you are typing stuff into until it shows up. Using build 2002051608, have seen it on yesterday's 2002052108 build and the problem goes back to at least April, maybe further. OS is Win2k Professional all latest SPs, Hotfixes, and Windows Updates.
I see this most on pages with forms, to me it seems like the cursor is perhaps getting stuck inside an invisible object. As I'm currently writing a web interface to an app, most every page I make involves forms, and a majority of the time I have this problem. It affects every view except source editor. Please try to fix this, it is a major issue.
Ok, apparently moving the cursors brings back the mouse, probably 100% of the time, this may be a dup of bug 130971.
*** Bug 148664 has been marked as a duplicate of this bug. ***
Still happens in 2002070708 build for win2k: I can reproduce it when I select/hilite multiple empty lines in the "HTML-Source" tab.
-->core based on comment 3 is this only broken on the trunk or is it also broken on the 1.0 branch builds?
Assignee: syd → kin
Component: Editor: Composer → Editor: Core
Keywords: regression
Summary: Composer text cursor invisible → text caret invisible (doesn't blink)
Whiteboard: EDITORBASE
Changing summary from: text caret invisible (doesn't blink) To: Caret not displayed in composer with pages containing readonly or disabled text widgets
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: text caret invisible (doesn't blink) → Caret not displayed in composer with pages containing readonly or disabled text widgets
Target Milestone: --- → mozilla1.1beta
Attached file Test Case (obsolete) —
It looks like this bug is also in Netscape 6.2. I think it has to do with the fact that under the covers there is only one caret per pres-shell that is shared with both the outer document and all text widgets on the page.
Assignee: kin → mjudge
Status: ASSIGNED → NEW
we had an over agressive disabling of the caret. We do not need to disable it. the caret will blink or not blink dependant on focus after the text control is created.
Status: NEW → ASSIGNED
fix and comment to stop disabling of caret. Disabling had the adverse effect of disabling the caret for the whole page not just the text control.
Comment on attachment 94176 [details] [diff] [review] patch for layout\html\forms\src\nsTextControlFrame.cpp sr=jag
Attachment #94176 - Flags: superreview+
Attachment #94176 - Flags: review+
Comment on attachment 94176 [details] [diff] [review] patch for layout\html\forms\src\nsTextControlFrame.cpp r=blythe
Can we have a unified diff with some more context please?
Comment on attachment 94176 [details] [diff] [review] patch for layout\html\forms\src\nsTextControlFrame.cpp please fix typo for "disableing" and capitalize it: Disabling
Attachment #94176 - Flags: needs-work+
Attached patch nsTextControlFrame.cpp (obsolete) — Splinter Review
spelling error fix
Attachment #93591 - Attachment is obsolete: true
Attachment #94176 - Attachment is obsolete: true
Attachment #94211 - Attachment description: textframepatch → nsTextControlFrame.cpp
Attachment #94211 - Flags: superreview+
Attachment #94211 - Flags: review+
Comment on attachment 94211 [details] [diff] [review] nsTextControlFrame.cpp please provide a diff with context (cvs diff -u4 nsTextControlFrame.cpp)
Attachment #94211 - Flags: needs-work+
more context to diff
Attachment #94211 - Attachment is obsolete: true
Comment on attachment 94232 [details] [diff] [review] patch with more context sr=sfraser
Attachment #94232 - Flags: superreview+
Comment on attachment 94232 [details] [diff] [review] patch with more context r=brade
Attachment #94232 - Flags: review+
*** Bug 133121 has been marked as a duplicate of this bug. ***
Note that you can also use the steps described in bug 133121 to test this, since in that case a disabled input field in a dialog revealed this problem.
checked into trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
marking fixed since its in the trunk
verified in 9/6 build
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: