Closed
Bug 34896
Opened 25 years ago
Closed 24 years ago
text widgets should use anonymous content
Categories
(Core :: DOM: Editor, defect, P1)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: mjudge, Assigned: mjudge)
References
Details
(Whiteboard: [nsbeta2+]Exception Feature)
Reducing ender down to the minimum of instantiations. Rather than lazy
instantiations, we place the editor on top of anonymous content.
1. Make a new widget with a view and an anonymous DIV.
2. Make an editor attached to that widget and initialize with a given selection
object as well as a content node(aka the DIV)
3. Make selection PER one of these widgets. make an interface to allow querying
of display selection ON/OFF.
4. Implement all the stuff that the old widget did.
5. fix all bugs before checkin in.
Comment 1•25 years ago
|
||
cc akkana
OS: Windows NT → All
Hardware: PC → All
Target Milestone: --- → M16
*** Bug 34982 has been marked as a duplicate of this bug. ***
Comment 4•25 years ago
|
||
new summary per team meeting
Summary: Editor Lite → text widgets should use anonymous content
Comment 5•24 years ago
|
||
this is the rework that Mike is doing for "ender lite" this is a must fix for
beta2
Putting on [nsbeta2+] radar for beta2 fix.
QA Contact: nobody → sujay
Whiteboard: [nsbeta2+]
Comment 7•24 years ago
|
||
moving from architecture to browser product
Product: Architecture → Browser
Version: 5.0 → other
this is almost ready to go just putting finishing touches on it.
Status: NEW → ASSIGNED
once again into the breach. i desperately want to get this to wrap i will not
even set a break point because i a SOOO sure this is going to work . fore score
and seven years ago.
Comment 10•24 years ago
|
||
Giving [nsbeta2+]Exception Feature status.
Whiteboard: [nsbeta2+] → [nsbeta2+]Exception Feature
Assignee | ||
Comment 11•24 years ago
|
||
one more thing. ender-lite turns out does NOT fix this problem. sorry i mislead
people i didnt realize the problem well enough before.
Assignee | ||
Comment 12•24 years ago
|
||
turned it on now. any problems lets solve them 1 at a time with more bugs.
thanks
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 13•24 years ago
|
||
Mike can you help me verifdy this one?
Assignee | ||
Comment 14•24 years ago
|
||
this is definately fixed. the only fear now is of other problems it may cause...
Status: RESOLVED → VERIFIED
Comment 15•24 years ago
|
||
Hi Michael and Akkana,
nsGfxTextControlFrame::SetFocus() calls nsIWidget->SetFocus()
but nsGfxTextControlFrame2::SetFocus() is just null and
doesn't call anything. Is there any reason?
It seems that the changes causes 42263, widget/src/gtk/nsWidget could not
get the SetFocus() call for proper nsIWidget.
UNIX IME can not get the exact Widget by SetFocus() call
so can not manage the input context properly. Could you
implement SetFocus() in nsGfxTextControlFrame2::SetFocus()
to call nsIWidget->SetFocus()?
You need to log in
before you can comment on or make changes to this bug.
Description
•