168485 - Want more editor API exposed to JS

Status: RESOLVED INVALID

(Core :: DOM: Editor, enhancement, P5)

Description

[[e-mail]]

It's a bit of a slog doing arbitrary editing in JS. Exposing more of the helper
methods would be a great help. Such methods include (with current C++ object):
nsIEditor.MoveNode
nsIEditor.GetChildOffset
nsIEditor.RemoveContainer
nsIHTMLEditor.RemoveBlockContainer
No editor methods appear to reverse the effect of RemoveBlockContainer - at
least there doesn't appear to be an easy way to determine the first and last
nodes that should be put in the block :-(

Comment 1

[Kathleen :Brade]

ew! do we really want to do this?  Can we come up with some commands to do instead?

Comment 2

[Akkana Peck]

I like the idea of exposing new stuff via commands rather than nsI*Editor APIs.

Comment 3

[[e-mail]]

Um, exactly how am I supposed to use a command to insert a container element?

Comment 4

[Joe Francis]

plus, text services eventually needs this stuff plus exposure of nsRangeUpdater

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Jens Stutte [:jstutte]]

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.

Comment 7

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Currently, we don't expose new API with XPCOM interface unless it's reqired by Thunderbird or SeaMonkey. If you are one of developers of them, please file a new bug to request every new API instead of this kind of meta like bug.