Open
Bug 95657
Opened 23 years ago
Updated 4 years ago
lose caret after adding anchor
Categories
(Core :: DOM: Editor, defect, P5)
Core
DOM: Editor
Tracking
()
NEW
Future
People
(Reporter: sujay, Unassigned)
References
Details
(Whiteboard: [caret][selection])
Attachments
(1 file)
237 bytes,
text/html
|
Details |
using 8/15 build of netscape 1) launch netscape 2) launch composer 3) insert some text 4) on that same line immediately after the text, insert anchor now try inserting the caret either after the anchor or below the text you entered. can't do it. looks like we don't insert a <br> after the anchor workaround = if you keep typing after the anchor then you can see the caret.
Comment 1•23 years ago
|
||
the caret is there, it just isn't rendering until the first character is typed.
Assignee: beppe → sfraser
Priority: -- → P2
Whiteboard: [care]
Target Milestone: --- → mozilla0.9.4
There are a couple of problems here. One is that clicking below the HR, seems to place the caret before the HR. This looks like a bug in nsFrame::GetContentAndOffsetsFromPoint(), which can be fixed with the following patch: Index: nsFrame.cpp =================================================================== RCS file: /cvsroot/mozilla/layout/html/base/src/nsFrame.cpp,v retrieving revision 3.327 diff -u -r3.327 nsFrame.cpp --- nsFrame.cpp 2001/09/19 12:34:48 3.327 +++ nsFrame.cpp 2001/09/27 00:16:20 @@ -1811,7 +1811,7 @@ aContentOffsetEnd = aContentOffset +1; else { - if ((thisRect.x + thisRect.width) < aPoint.x || thisRect.y > aPoint.y) + if ((thisRect.x + thisRect.width) < aPoint.x || (thisRect.y + thisRect.height) <= aPoint.y) { aBeginFrameContent = PR_FALSE; aContentOffset++; The 2nd problem seems to be that mjudge added some code to nsFrame::IsSelectable() which prevents us from placing the caret when clicking just after the HR. Sending this over to mjudge. (selection owner)
Priority: P2 → --
Whiteboard: [care] → [caret][selection]
Target Milestone: mozilla0.9.5 → ---
when I get a chance to rework the snapping caret all these will go away. until then i am shoving this into future
Target Milestone: --- → Future
*** Bug 114310 has been marked as a duplicate of this bug. ***
Updated•18 years ago
|
QA Contact: sujay → editor
Updated•18 years ago
|
Assignee: mjudge → nobody
Comment 8•14 years ago
|
||
This issue is still there in current trunk build.
Comment 9•4 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.
If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•