# Why the editor functionality was changed?

**URL:** https://meta.discourse.org/t/why-the-editor-functionality-was-changed/35357
**Category:** Bug
**Tags:** composer
**Created:** [November 8, 2015, 3:55pm UTC](https://meta.discourse.org/t/why-the-editor-functionality-was-changed/35357 "2015-11-08T15:55:46Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Steven](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steven/32/187890_2.png) [@Steven](https://meta.discourse.org/u/Steven)
#### Post date: [November 8, 2015, 3:59pm UTC](https://meta.discourse.org/t/why-the-editor-functionality-was-changed/35357/2 "2015-11-08T15:59:23Z")

</div>

The composer is currently being (completely) rewritten by the Discourse Team, there still are some bugs but it will be fixed soon

> [@Help us test the rewritten Composer](https://meta.discourse.org/t/help-us-test-the-rewritten-composer/34679):
>
> We’ve been using [pagedown](https://code.google.com/p/pagedown/) as our rich composer for years. Unfortunately, we’d outgrown it in a few ways: It’s very hard to extend to add features. It hasn’t been updated in years. It had implementations of features we didn’t like or found buggy like undo/redo. We forked the editor and removed them but that just left us with a lot of dead code. It had zero tests. Modifying it meant we could be taking a detour to regression town U.S.A. We made the decision to rewrite our composer us…

---

_[View the full topic](https://meta.discourse.org/t/why-the-editor-functionality-was-changed/35357)._
