Component: General → Editor
Product: Firefox → Core
QA Contact: general → editor
This is a problem and a major barrier for wikEd, which is used on many various wikis in order to improve their user's experience. Rich text editors for things like blogs are also exist and this bug interferes with them as well.
Yes, if you fix this, you can really help out wikipedia.
Do other browsers do better here? If so, how? If not, it seems like changing our behavior might pose compatibility problems, and a better forum for developing a solution might be the WHATWG list.
The others do not do better as far as I know. I agree that the introduction of new options and commands should finally be discussed and decided by WHATWG or another standardizing instance. However, it would not hurt to brainstorm some possible solutions here first with people that know more about the actual details of the Midas implementation. Some of the possible solutions (or at least temporary fixes) proposed above lay at the discretion of of the browser implementations and it is hard to imagine how the fine tuning of the undo/redo functionality could introduce unwanted browser incompatibilities.
I know very little about the programing end of things but I do know that as a Wikipedia editor, the project WikEd that Cacycle is working on is the best thing since sliced bread. Such text editors are the future for Wiki projects.
blocking2.0: --- → ?
9 years ago
Summary: Automatic syntax highlighting interferes with undo/redo history in rich text editors → add mechanism for editing libraries to make changes separately from the undo/redo stack (Automatic syntax highlighting interferes with undo/redo history in rich text editors)
9 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
blocking2.0: ? → -
You need to log in before you can comment on or make changes to this bug.