Open Bug 168485 Opened 19 years ago Updated 12 years ago

Want more editor API exposed to JS

Categories

(Core :: DOM: Editor, enhancement)

enhancement
Not set
normal

Tracking

()

UNCONFIRMED

People

(Reporter: neil, Unassigned)

Details

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 :-(
ew! do we really want to do this?  Can we come up with some commands to do instead?
OS: Windows 95 → All
Hardware: PC → All
I like the idea of exposing new stuff via commands rather than nsI*Editor APIs.
Um, exactly how am I supposed to use a command to insert a container element?
plus, text services eventually needs this stuff plus exposure of nsRangeUpdater
Target Milestone: --- → Future
Product: Browser → Seamonkey
Assignee: mozeditor → nobody
QA Contact: sujay → composer
Target Milestone: Future → ---
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
Status: NEW → UNCONFIRMED
Component: Composer → Editor
Product: SeaMonkey → Core
QA Contact: composer → editor
You need to log in before you can comment on or make changes to this bug.