Create separate plugin for contentEditable=false
|Reported by:||alfonsoml||Owned by:||alfonsoml|
|Component:||Core : Read-only||Version:|
In order to support correctly contentEditable=false there are a number of additions to the normal code and that means a general performance hit that should required only for those systems where such non-editable elements are being used.
By moving some functions to a separate plugin we can avoid most of the performance hit as well as allowing to keep improving such support without a degradation for the rest of uses.
Change History (7)
Changed 6 years ago by alfonsoml
comment:4 Changed 3 years ago by Reinmar
- Resolution set to wontfix
- Status changed from review_failed to closed