# Discourse Basic Editor

**URL:** https://meta.discourse.org/t/discourse-basic-editor/159431
**Category:** Plugin
**Tags:** broken
**Created:** [July 31, 2020, 4:00pm UTC](https://meta.discourse.org/t/discourse-basic-editor/159431 "2020-07-31T16:00:55Z")
**Posts on this page:** 1
**Showing post:** 98

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [October 30, 2023, 4:45am UTC](https://meta.discourse.org/t/discourse-basic-editor/159431/98 "2023-10-30T04:45:20Z")

</div>

> [@spirobel](#):
>
> There are better ways to spend free time than trying to swim against the tide of a large open source project.

I wrote about this problem here:

> [@Markdown syntax highlighting in post editor](https://meta.discourse.org/t/markdown-syntax-highlighting-in-post-editor/282665/10):
>
> Just to expand, first that this is something I really want core to support but also worth expanding on the complexity. Discourse core uses many many APIs against TEXTAREA directly, @mentions, toolbar inserts stuff into the TEXTAREA, uploads, cut and paste images and more. This is all not abstracted away and assumes it is talking to a TEXTAREA. Adding a contenteditable there direct would mean it would need to also properly and very accurately simulate a TEXTAREA, something that is likely to fai…

We will get to adding first class support for ContentEditable and other types of composers, it is just going to take a while longer.

---

_[View the full topic](https://meta.discourse.org/t/discourse-basic-editor/159431)._
