24 Comments

  1. Vinny O'Hare
    · Reply

    Hopefully you can turn this off? Have never used the full screen editor and have no plans. Now I have to teach a team on this change.

    Report

  2. Louis
    · Reply

    Another example of discussion and democracy NOT being present whenever MW decides to do something.

    Matt’s way or the highway. That’s what it is. It is his to do with as he pleases. Nobody using WordPress should be surprised. He’s got the market share, he has the power. Either we get used to it or …. well …. we get used to it.

    Report

    • Justin Tadlock
      · Reply

      It should be noted that the decision-making structure for WordPress has never been democratic. It is more based on merit with the project lead, the final decision-maker, at the top.

      I am willing to take Matt at his word that the feedback and testing show that fullscreen mode is a better experience, but I would rather see the data behind that. I am not a fan of pushing such a change so late in the dev cycle, particularly if it’s something that could have waited and become a better experience (e.g., perma-storing the preference via user metadata).

      Criticism of ideas and decisions is discussion worth having in the comments. Simply being critical of a person is not and tends to lead the discussion astray.

      Report

  3. Terje Skuggen
    · Reply

    Still I would recommend you to try Gutenberg if not for something else than playing around with differen blocks. It is the future and it’s not going away.

    I still play around with both of them but I find myself using Gutenberg more and more. Classic Editor is fine for now but it will disapperar sooner or later.

    Report

  4. Sue
    · Reply

    Now, all my images in the editor display as a horizontal/rectangle image. Then when I preview, they are square in live mode. I hate the horizontal image as it does not show the real look of the image. Can this be changed?

    Report

  5. T Piwowar
    · Reply

    With so many broken and missing bits in WP it is sad to see time wasted on such uselessness. Why should I need to add 50 plugins to run a very basic community website?

    Report

  6. Tro
    · Reply

    This is a step in the right direction. I’m very happy to hear this. Now that full screen is the default, the Gutenberg contributors can better work on making the content look like the live page, to make Gutenberg a WYSIWYG page builder.

    Report

  7. David Brown
    · Reply

    Yet another poorly-thought-through change in a release cycle that has been a case study in how to not build software.

    Report

  8. Michael
    · Reply

    Great article and I’m not worried about the change. In fact, I like it that way. Also, Classic or Gutenberg are welcome in my book

    Report

  9. Ben
    · Reply

    It would also be nice if editor preferences were a user meta setting stored in the database and not just stored in local storage as this is right now. Local storage is not very… permanent. Simply changing browsers (or even running the browser in private mode) will cause users to end up in radically different editing experiences without warning. I foresee lots of forum support questions about how to get out of full-screen editor mode and then even more with “why does it keep switching back”.

    Report

  10. kevin kovadia
    · Reply

    I am really happy that wp team is coming up with full-screen editor option in next release. I tried it using the beta tester plugin. It gives us a smooth and realistic editing experience like new google sites. I am also looking forward to trying the front end editor.in WP.

    Report

  11. Lee
    · Reply

    Ah, yes, this will be as useful as that full-screen mode in the classic editor that everybody didn’t like.

    Forcing creators to use full-screen mode is an example bad UI design decision making. End-users must be in full control of their dashboard settings.

    Overriding the end user’s preferences and settings is rarely ever a good idea and is often forever remembered in all the wrong ways.

    Remember that time WordPress wanted to force people to use Gutenberg..?

    Remember that time WordPress wanted to force people to use full-screen mode..?

    Remember that CMS everyone used to use. What was it called..? WordThingy or something..?

    I’m a fan of Gutenberg. I predicted WordPress would move toward the page builder + minimalist theme stack many years ago. Long before Gutenberg arrived. But, keep making bad decisions like this that remove choice from end-users or that override end-user settings and WordPress will go the way of that other CMS.. what was that CMS called again.. WordThingy or something?

    Let end-users make their own decisions. Offer full-screen mode as an option. Give it big button to switch it on and off. Don’t tell people they must disable it after they have become accustomed to never having need to enable it, ever.

    Report

  12. Bastian
    · Reply

    One of the most mystifying things about the WordPress team is their persistent fascination with fullscreen/non-distracting/whatever modes.

    Report

  13. Ben Sibley
    · Reply

    Anyone who wants to use the Fullscreen mode is already using it. If they believe people aren’t using it because they don’t know about it, then add a tooltip over the menu (which most users probably never open) and tell them about it.

    Changing the user’s settings without their approval is not in the spirit of “democratizing publishing”. This is going to piss off a lot of people. And honestly, everyone will get over it, but a massive number of people are going to have their workday disrupted and have to search the interface to find a hidden button to return the menu and likely need to Google the solution. The end result is people learning that WP updates stink because they change their settings without asking and disrupt their workflow.

    Report

  14. Rod Olman
    · Reply

    Lots of negativity here. Why? Ever since Gutenberg was forced into the core WordPress has been one opaque, secret decision after the other.

    Making the editor full-screen per default, without the option to permanently disable it, is just another breaking change (not to mention the various CSS breakages between GB versions which forces theme and plugin authors to go through their code again after each GB release).

    Report

  15. Juanma Aranda
    · Reply

    From my point of view, and based on the tests I have done, for the full screen format to be useful, we need to solve at least two very important things first:
    1. That the canvas in which the blocks are inserted also occupies the width of the screen. This would be extremely useful for working with groups of blocks, especially when they include multiple columns to which text must be added. If the full screen leaves a canvas just as small as previously anchored in the center of the screen, what’s the point?

    Replace the upper left button (arrow) so that the administration menu reappears instead of taking you to the list of entries, which does not make any sense in the editor.
    By inertia, the user is used to collapsing the admin panel and customizer menus and redisplaying them by clicking an arrow they expect to find …

    I really think that those in charge of programming do not use the block editor too much in their day to day … they are obvious things that they leave behind while they want to advance in other functions that are not so necessary yet.

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: