Opened 14 years ago
Closed 10 years ago
#6116 closed Bug (wontfix)
The contentEditable attribute is lost from textareas and inputs
| Reported by: | Sa'ar Zac Elias | Owned by: | Sa'ar Zac Elias |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | 3.4 Beta |
| Keywords: | Cc: |
Description
- Load the following:
<textarea contentEditable="false">Text</textarea>
- Go to source mode.
Notice that the attribute is missing.
Attachments (1)
Change History (5)
comment:1 Changed 14 years ago by
| Milestone: | → CKEditor 3.4 |
|---|---|
| Owner: | set to Sa'ar Zac Elias |
| Status: | new → assigned |
Changed 14 years ago by
| Attachment: | 6116.patch added |
|---|
comment:2 Changed 14 years ago by
| Status: | assigned → review |
|---|
comment:3 Changed 14 years ago by
| Milestone: | CKEditor 3.4 |
|---|---|
| Status: | review → review_failed |
comment:4 Changed 10 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | review_failed → closed |
It would be a waste of time and unnecessary code bloating.
Note: See
TracTickets for help on using
tickets.
I don't think it's worth having code changes because of this one. In fact, using contenteditable in form fields is a very uncommon practice. So, let's wait for some one coming with this need from the real world.
Additionally, this issue also impacts <input> elements.
Even when considering the fix needed, I would make it inside the protectReadOnly and unprotectReadyOnly functions directly, instead of bringing overhead to processor.