Opened 16 years ago
Closed 16 years ago
#3002 closed Bug (fixed)
Use "filters" for the htmlParser API
| Reported by: | Frederico Caldeira Knabben | Owned by: | Frederico Caldeira Knabben |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.0 |
| Component: | General | Version: | |
| Keywords: | Confirmed Review+ | Cc: |
Description
Currently, we are introducing specific output manipulation directly into the domParser code. This makes that code quite hard to maintain, and less flexible, as it is not able to customize the manipulation with easy.
There should be instead a way to attach a "filter" to the parser, including all necessary rules for it.
In this the data processor can have a public filter property, which can be easily modified by a plugin or external code.
Attachments (1)
Change History (5)
Changed 16 years ago by
| Attachment: | 3002.patch added |
|---|
comment:1 Changed 16 years ago by
| Keywords: | Review? added |
|---|---|
| Status: | new → assigned |
comment:3 Changed 16 years ago by
| Keywords: | Review+ added; Review? removed |
|---|
Note: See
TracTickets for help on using
tickets.
The provided patch introduces a quite drastic change in the way we manipulate data. It now parses it not only on output, but also on input (see #3003). Also, all the data transformation logic is now modular, so plugins can easily include their own filtering rules. The fakeobject system now uses it.