1. Ted Magwell

    Oh no, please don’t, it’s already laggy. Gutenberg badly needs to reduce the amount of JavaScript – lazy load more modules.


  2. Gemma Grace

    5 million sites are using the Classic Editor plugin because it provides a way of editing text which doesn’t require animation to understand basic interactions such as moving a paragraph.

    Adding animation on top of a user interface where people find simple interactions confusing isn’t the answer.

    Please stop over-engineering.


  3. Daniel James

    I hope that the prefers-reduced-motion media query is included with anything that ships with that kind of motion in core because that could after a while become quite jarring to see.


    • Kjell

      Matías does mention this media query in his post, and it is definitely a priority for the team. `prefers-reduced-motion` support is active for all animations and transitions in Gutenberg, including the ones driven by `react-spring` (the js animation library that Matías mentions in his post).


  4. Bastian

    these concerns were often brushed aside as coming from people who were resistant to change.

    And they continue to be brushed aside. Nothing has changed.


  5. Thomas Burke

    I find this statement here: “…it’s important to recognize that these kinds of refinements to interactions take time to percolate…” to be quite incongruent considering how fast and furiously Gutenberg in its highly flawed state was forced onto users with no option to avoid it unless we installed some OTHER plugin to get rid of it.

    Our company currently uses Disable Gutenberg to get rid of Gutenberg, and I am actively following the Classic Press fork, as well as pushing for a complete redesign to get away from WordPress–due to what the “team” did by forcing this terrible block interface onto users. What a disaster–and I suspect it is the reason why WordPress was noted as the most dreaded platform by developers this year.


Comments are closed.

%d bloggers like this: