Closed
Bug 13887
Opened 25 years ago
Closed 25 years ago
[dogfood] in composer, editor never gets a Focus notification
Categories
(Core :: DOM: Editor, defect, P1)
Tracking
()
M11
People
(Reporter: buster, Assigned: hyatt)
References
()
Details
(Whiteboard: [PDT-])
launch editor from browser task menu, so default edit page loads
notice the caret, it's above the first line of text and really small
the selection at this point is Sel. Collapse to 031F90AC __moz_text 0 according
to debug output (turning on DEBUG_SELECTION in nsRangeList.cpp)
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 1•25 years ago
|
||
This is because the caret is in a text node which contains just whitespace. I
think the code that sets the initial selection for the editor needs to be a bit
smarter.
Comment 2•25 years ago
|
||
Could someone point me at the code where this might be addressed?
Updated•25 years ago
|
Assignee: sfraser → buster
Status: ASSIGNED → NEW
Comment 3•25 years ago
|
||
Reassigning this, due to current focus on performance issues.
Steve, IsEditable needs to return true for <BR> nodes/frames, so that the caret
ends up being placed on the first one. What happens now, in mail compose, is that
the caret ends up in the signature, because that's the first node that contains
text.
Status: NEW → ASSIGNED
Summary: caret in odd place when editor launched → [blocker] caret in odd place when editor launched
Whiteboard: fix in hand, waiting for permission
Target Milestone: M11 → M10
this looks like a usability blocker, quite easy to fix, very low risk. simon
has already code reviewed.
Comment 5•25 years ago
|
||
ok. checkin. thanks
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: fix in hand, waiting for permission
Comment 9•25 years ago
|
||
Using the 19999100618 M10 candidate commercial build on NT, I'm seeing the caret
appear initially before the "H", and then disappear.
User must click in document in order for the caret to reappear.
Comment 10•25 years ago
|
||
Moving to M11. sujay, please Release Note for M10 at:
http://bugzilla.mozilla.org/show_bug.cgi?id=14872
Reporter | ||
Comment 11•25 years ago
|
||
I think this is simply the content area failing to get focus. Selection is set
in the correct place in the document.
Summary: [blocker] caret in odd place when editor launched → [dogfood] caret in odd place when editor launched
Reporter | ||
Comment 12•25 years ago
|
||
marking dogfood, because it makes the app a pain to use. removing blocker,
since no one is actually blocked on this. Sent a note to simon, hyatt, and pink
asking about focus.
Summary: [dogfood] caret in odd place when editor launched → [dogfood-pd-] caret in odd place when editor launched
Comment 13•25 years ago
|
||
Not a dogfood blocker. sorry...adding pdt-
Summary: [dogfood-pd-] caret in odd place when editor launched → [dogfood][pd-]caret in odd place when editor launched
Summary: [dogfood][pd-]caret in odd place when editor launched → [dogfood][PDT-]caret in odd place when editor launched
Summary: [dogfood][PDT-]caret in odd place when editor launched → [dogfood]caret in odd place when editor launched
Whiteboard: [PDT-]
Assignee: buster → hyatt
Status: REOPENED → NEW
Summary: [dogfood]caret in odd place when editor launched → [dogfood] in composer, editor never gets a Focus notification
Reporter | ||
Comment 14•25 years ago
|
||
with recent focus change landings, I think this got broken. The problem is the
editor never gets a focus message. Set a break in
nsTextEditorFocusListener::Focus(nsIDOMEvent* aEvent),
run apprunner -edit
editor focus handler never gets called. It used to, it still should.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
Comment 15•25 years ago
|
||
*** This bug has been marked as a duplicate of 9701 ***
Comment 16•25 years ago
|
||
verified in 10/22 build.
You need to log in
before you can comment on or make changes to this bug.
Description
•