Closed Bug 45487 Opened 25 years ago Closed 4 years ago

Editor Rules/Behavior Bindings Language

Categories

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

enhancement

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: kinmoz, Unassigned)

Details

It would be cool if we had some sort of mechanism that allowed us to read in an external file that contained the editing behaviors we expect. I'm thinking it would be CSS or XBL like.
Setting milestone to future since it's an RFE.
Target Milestone: --- → Future
accepting bug
Status: NEW → ASSIGNED
Joe, I discover this bug only now ; we had a discussion about this exact subject last time we met in MV. I think that such a language is an important issue for (a) the maintainability of editing rules (b) the extensibility of editing rules to other XML languages than HTML4 (c) footprint. We should resurrect this bug in a close future and write down some ideas about such a language. I feel it could be a real plus. Please make sure to read a spec I wrote some time ago that could be a starting point for a css-alike language : http://www.w3.org/TR/NOTE-STTS3
I need you or someone else to describe to me how this would work. I don't grok how I can do all the things I need to do with such a language, unless that language has the power of C++.
removing myself from the cc list
Should this bug be dependant on bug 30838? Fixing them should make all editing rule/behaviour implementable in javascript. In fact I don't see how it can't just modify browser dom to create the editing effect. Forgive my ignorance for saying this, but wouldn't this obsolute nsIeditor? Except nsIeditor would be a bit faster? For example the mathml editor is implemented in iframe.
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Summary: [RFE] Editor Rules/Behavior Bindings Language → Editor Rules/Behavior Bindings Language
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

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

Severity: normal → S4
Priority: P3 → P5

In these days, editor's perfomance and consistency between browses are more important than 20 years ago. And now, beforeinput was shipped to make web apps and extensions possible to override default behavior. So, we don't need this kind of complicated feature in the Core.

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