what happened to the old css editor?

  • Resolved Owen

    (@owensj)


    11 years ago

    Hi,
    Recently updated to the latest Jetpack version and I love the new features. However I prefer the old css editor as it put up warnings and gave me helpful info and lots more. What happened to the old one? Why was it changed?
    Here is my site if you need to look at it.

    https://www.ads-software.com/plugins/jetpack/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    The Custom CSS editor was previously powered by Ace. In 2.6, we updated the module and now use another library, named Codemirror. You can find several articles on Google comparing the 2 editors, and both editors obviously have their pros and cons, but we chose to move to Codemirror for several reasons. Here are a few:

    • Ace was huge. Codemirror, on the hand, is a lot smaller; the entire library is only 131.7kb, compared to 579.9kb for Ace, or roughly 22.7% the size of the older editor.
    • The Ace editor overrode a lot of browser functionality and broke a few of your usual browser keyboard shortcuts. Codemirror is better about not breaking normal browser behaviour.
    • Implementing Codemirror allowed us to fix several outstanding bugs with the old editor. Syntax highlighting is now better, tab management is also better, among other things.
    • The new editor is better integrated with WordPress Core.

    I hope this clarifies things a bit.
    You can find a summary of the changes in the following changesets:
    https://plugins.trac.www.ads-software.com/changeset/795348
    https://plugins.trac.www.ads-software.com/changeset/795350
    https://plugins.trac.www.ads-software.com/changeset/802710

    Thread Starter Owen

    (@owensj)

    ok thanks jeremy after reading the pros I don’t blame you to switch to codemirror

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘what happened to the old css editor?’ is closed to new replies.