Closed Bug 10756 Opened 25 years ago Closed 29 days ago

logging every selection doesn't allow for property changes

Categories

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

defect

Tracking

()

RESOLVED INCOMPLETE
Future

People

(Reporter: Brade, Unassigned)

Details

(Keywords: helpwanted)

When logging, you can't replay the commands to change the style since they are
lost when the selection is reset.

For example, in an empty document log the following steps:
 * type:  abc
 * click the bold icon
 * type:  def

Notice that in the log, the selection is set between each keystroke and command.
This means that setting bold won't work since the editor thinks that the
selection has changed (so the bold command is ignored).
Status: NEW → ASSIGNED
Target Milestone: M11
Accepting bug, setting milestone to M11.

Just wanted to note that you can replay style changes that are applied to
selected (hilighted) content. This bug happens when trying to apply a style when
the selection is a caret.
By the way, the temporary workaround for this is to edit the journal.js file and
comment out the calls to EditorSetSelectionFromOffset() before every call to
SetTextProperty.
Oops, screwed up on the workaround description above.

Comment out the call to EditorSetSelectionFromOffset() AFTER the call to
window.editorShell.SetTextProperty(), ONLY if the selection offsets for the
SetTextProperty() call match the selection offsets after it.
Moving some SpellChecker/TextServices feature requests and bugs, that can wait
till after beta 1, to milestone M14.
Moved to M15 to balance bug counts across milestones.
Moving all non-beta1 bugs to M16 since I am going on sabbatical.
Target Milestone: M15 → M16
moving to m17
Target Milestone: M16 → M17
Target Milestone: M17 → M19
Move to M19.
setting to future, although this was a great tool for QA to use for debugging
Target Milestone: M19 → Future
adding help wanted keyword
Keywords: helpwanted
QA Contact: sujay → editor
Assignee: kinmoz → nobody
Status: ASSIGNED → NEW

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5

The original report was for the editor application, which is a very different scope from the current DOM:Editor. EditorSetSelectionFromOffset() is no longer in m-c.

Status: NEW → RESOLVED
Closed: 29 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.