Closed Bug 34477 Opened 25 years ago Closed 22 years ago

Editor embedding tracking bug

Categories

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

defect

Tracking

()

VERIFIED DUPLICATE of bug 157128
mozilla1.0.1

People

(Reporter: rusty.lynch, Assigned: mjudge)

References

Details

(Keywords: embed, meta, topembed, Whiteboard: [TRACKING])

Not too long ago, the editor was not required for simple web browsing. Recently a dependancy has been added for the editor in order to type into form input fields. For running embedded mozilla apps on small devices this is a real limitation since the editor library, libender.so, is very large. If an embeded app doesn't want to use the editor like composer or as a mail/news client, then the app shouldn't have to carry around the extra library luggage. Has anyone else thought about this?
Status: UNCONFIRMED → NEW
Ever confirmed: true
We do need to provide a skeleton of the editor library for samller devices, providing mozilla with a subset of the code. Eliminating HTML specific code, possibly undo/redo, etc. Assigning to Kin to spearhead the investigation and cc remainder of the team.
Assignee: beppe → kin
Can someone clarify this point for me: I assume we'll still need some "HTML" editing stuff so that we can show IME input highlighting or spellcheck highlighting or ? True?
Hardware: PC → All
Target Milestone: --- → M17
I can speak from my needs as an embedded mozilla developer on a resource limited device. I am not using any of the IME functionality in the editor library. So, for me all I need is the ability to enter/delete text in text area's and input fields. I posted a message on the embedding and small-devices news groups to try to get input from other developers with simular constraints.
Currently, text widgets are implemented using composer on top of an HTML subdocument, and typing in such a widget will involve much of the code in the editor DLL. It would be non-trivial to split up the editor library so that a smaller version of the library could be used for widget-only apps.
Accepting bug.
Status: NEW → ASSIGNED
assigning this bug to sfraser as the embedding tracking bug, cc kin as well
Assignee: kin → sfraser
Status: ASSIGNED → NEW
updated summary to reflect the new standing of this bug
Summary: Editor library required for form input fields → Editor embedding tracking bug
Target Milestone: M17 → M20
added embed keyword
Keywords: embed
Whiteboard: [TRACKING]
Mo zill a
Status: NEW → ASSIGNED
Target Milestone: M20 → mozilla0.9
Depends on: 62035
Adding dependency on the font list bug 62035.
Depends on: 26288
No longer depends on: 62035
Assignee: sfraser → beppe
Status: ASSIGNED → NEW
reassigning to me for tracking purpose, will be adding dependency on task bugs
Depends on: 66290
Depends on: 66294
Depends on: 66296
Depends on: 66300
Depends on: 66305
Depends on: 66307
Depends on: 66308
Depends on: 66318
Depends on: 66343
Depends on: 66344
Depends on: 66345
Depends on: 66351
Depends on: 66352
Depends on: 66353
Add skin switching bug 43350.
Depends on: 43350
Blocks: 67993
Blocks: 64833
moving to mozilla1.0
Target Milestone: mozilla0.9 → mozilla1.0
Blocks: 70229
removing 26288 from the tracking
No longer depends on: 26288
-->chofmann
Assignee: beppe → chofmann
add valeski
Blocks: 103889
No longer blocks: 64833
giving this to mjudge as a starting point for tracking the editor embedding work
Assignee: chofmann → mjudge
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
don't move bugs that are in the 1.0 dependency tree. sorry.
Target Milestone: mozilla1.0.1 → mozilla1.0
Keywords: meta
Keywords: topembed
removing myself from the cc list
No need to mark tracking bugs with 'topembed'.
Keywords: topembed
Target Milestone: mozilla1.0 → mozilla1.0.1
Depends on: 122574
Ummm. What is this bug for? It seems the real embedding tracking bug is bug 157128?
This is a duplicate of bug 157128 (or vice versa) but the following are not on bug 157128: 66343: not sure if this is necessary; what is the state of text services? 66344: I would argue this is not a dependency at all as long as it is possible for someone to be able to write an extension. 41301: iframe is editable instead of page 70229: embedding api todo list (is this now obsolete?) 103889: layout group tracking bug (is that bug obsolete or being actively used?) This bug is missing these bugs (possibly more?): 79895: editortypes 121648: editorshell removal 133598: <editor> tag in xul (cleanup) 137173: embedding fileset is incomplete 157097: command nodes hold state 157098: command nodes need to trigger update 157100: sample Macintosh application 157101: sample Linux application 157104: use of nsIEditingSession in Composer/Mail/etc 157105: "make editable" api needs to be recursive 157106: remove docshell dependency on editor 157109: need api to iterate over all editors in a session 157111: make JS commands accessible to embedders 157114: remove code that points to xul command nodes 157116: doCommand should pass nsIEditor not nsIEditorShell as param 157117: sandboxing of editor
Saari, mjudge: Seems like we should dup this to bug 157128 and add bug 41301 and bug 70229 (and maybe bug 103889?) as blockers to that bug?
Keywords: topembed
Depends on: 170433
Keywords: topembed
Depends on: 171766
*** This bug has been marked as a duplicate of 157128 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
Blocks: grouper
Bulk adding topembed keyword. Gecko/embedding needed.
Keywords: topembed
You need to log in before you can comment on or make changes to this bug.