Make WordPress Core

Tagged: editor Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Ozz 4:39 am on October 28, 2016 Permalink |
    Tags: , , editor,   

    Editor changes in 4.7 

    There are a few noteworthy changes to the editor in WordPress 4.7.

    Some of the toolbar buttons have been rearranged to make them easier to access and to encourage proper use of the HTML elements they insert.  The headings drop down is now moved to the top row, and the strike-through and horizontal rule button are moved down. This also reflects their usage.

    The underline and justify buttons have been removed from the bottom row. Underlining is a bad practice as readers can confuse it with links (bad accessibility), and it does not insert a semantic element. Justifying has uneven browser implementation, and in many cases is bad for readability. Keyboard shortcuts for both will keep working.

    For more information see #27159 that also has links to the discussions in Slack.

    Labels for keyboard shortcuts have been added to the tooltips for buttons and inside drop downs to make them easier to discover.

    As always, feedback is welcome.

    Ella and Andrew

    • Fahid Javid 5:40 am on October 28, 2016 Permalink | Log in to Reply

      Nice improvements!

    • Retrofitter 6:42 am on October 28, 2016 Permalink | Log in to Reply

      Nice touch moving the header drop down, thanks

    • espiat 7:53 am on October 28, 2016 Permalink | Log in to Reply

      Perfect. Thanks.

    • Ahmad Awais 10:16 am on October 28, 2016 Permalink | Log in to Reply

      Nice, I was looking forward to this one. @azaozz just wondering, the feedback from folks on this ticket didn’t transition into props? I think for a ticket like this, feedback can be considered as much important as the contributions to any other ticket. Which essentially would have transitioned into `props`. Steps like this would help people engage more and help make/steer the core decisions. I remember on of the release leads talking about how much we should be generous when it comes to props (considering them equal for anyone giving back even if it is by providing feedback in a ticket like this one). Just my two cents.

    • catchmyfame 7:28 pm on October 28, 2016 Permalink | Log in to Reply

      Will this have any impact on your TinyMCE Advanced plugin?

    • Joy 12:12 am on October 30, 2016 Permalink | Log in to Reply

      Did any of the updates affect the Text mode toolbar? It needed some love.

    • avcascade 9:21 pm on October 30, 2016 Permalink | Log in to Reply

      Thumbs up for these changes. I would like to see a button in the editor that allows me to set a background color for selected text (e.g. yellow highlighting). Right now, it’s possible to set text color, but there’s not an option to easily highlight text.

    • Diego Betto 9:22 am on October 31, 2016 Permalink | Log in to Reply

      Oh thanks! keyboard shortcuts are awesome!

  • Andrew Ozz 2:00 am on July 29, 2016 Permalink
    Tags: , , editor, ,   

    Editor changes in 4.6 

    In WordPress 4.6 TinyMCE is upgraded from version 4.3.10 to 4.4.1. There are numerous bug fixes and several new features, most notably a new inline theme (changelog).

    The wpview editor plugin (that is responsible for showing gallery, video, audio, and oEmbed previews) was updated to use the TinyMCE API for non-editable elements. This brought some small changes and improvements in the UI, for example “views” are draggable now. On the back-end the wp-mce-view-unbind event was removed as it doesn’t exist in the API. It was intended for cleanup/unloading but was never very reliable. If a plugin needs to unload instance dependent scripts, it can use mutation observer to monitor when the view node is deleted. See #36434 for more information.

    wpview remains an experimental API, though with each iteration it is getting closer to being finalized. As an experimental API, breaking changes are expected. As always, please test your plugin now if it modifies or depends on the editor, especially if you use experimental features like wpview.

    • elliotcondon 4:08 am on August 29, 2016 Permalink | Log in to Reply

      Hi guys,

      Elliot here – ACF developer.

      I’ve just noticed an odd bug (maybe) in this version of tinymce. The tinymce JS object contains a function called ‘add’ which “Adds an editor instance to the editor collection”. This is run each time a tinymce editor is initiated.

      This function contains an odd line of code copied below which seems to ‘double’ up the ‘collection’:
      editors[editor.id] = editor;
      Note that the editor is added using the id (as expected), and then also ‘pushed’ (added again using a numeric key).

      if you check the console lo, you can see the collection using “tinymce.editors”. You can see each editor is added twice.

      Please also be aware that this function also changes the ‘activeEditor’ to the last added instance which is different to the WP JS that sets the wpActiveEditor value (to the first editor id).

      I hope this info has been useful. I’ve just updated the ACF PRO plugin with a fix to avoid some JS errors introduced by this (I think…)


    • Arno Kools 9:29 am on September 1, 2016 Permalink | Log in to Reply

      TinyMCE was NOT upgraded when upgrading WordPress to version 4.6.

      Version 4.3.10 was still used and it broke completely.
      I had to manually replace it with the latest version from the TinyMCE website.

    • enternetconnections.com 1:54 pm on November 10, 2016 Permalink | Log in to Reply

      I upgraded a woocommerce site to 4.6.1 so the content writer could use jet pack. Big mistake. Now tinymce editor is broken. The content writer can’t add or edit new posts and the owner can’t add or edit products (kept in the post table, I can’t imagine why products and orders don’t have their own table). I’ve googled this and so many people have issues, usually they complain to the theme writer and they take care of it. But he’s using the free mystyle theme. I’ve tried almost every fix out there, still no luck. I wish now I had made him use my own ecommerce code. If something isn’t working with that, I know right where to go fix it. WordPress is a beast. This guy is pulling his hair out.

  • Ella van Dorpe 10:57 pm on April 12, 2016 Permalink
    Tags: , editor   

    Editor wish list for 4.6 and beyond – chat summary 

    This list builds on the previous wish list. You can read the full chat in the archive.


    • Allow suggestions and comments to be made, similar to what ICE does. This would make a good plugin and feature project first. @eric and @azaozz seem to be interested in working on something like this.


    • (Publish) meta box revamp. See #36474. Feedback welcome! @michael-arestad, @melchoyce, @helen@mapk@hugobaeta?

      Proof of concept.

      Proof of concept.

    • More experimenting with inline toolbars (separate for formatting and inserting). We could first do this on small screens where the toolbar would be fixed at the top, later maybe on big screens. See also #29923.
    • Could editor scrolling be improved (e.g. hide on scroll down)? See #36482, and also #31751.
    • Caption placeholder. Focusing on an image would give you a placeholder for a caption. See #32175.
    • Leaving dialog. Offer WordPress UI on leaving the page if we can with the option to save changes. See #28566.
    • Advanced panel for the inline link toolbar, so plugins can add options. See #36312.
    • More formatting shortcuts (code blocks, bold, italic…)? See #36433, and also #6331.
      Decide whether to add bold and italic shortcuts at all, how to do the triple back tick shortcut.
      Try to merge with TinyMCE’s own textpattern plugin.
      Any other things we could automatically format in the editor? Curly quotes? Thinking about wptexturize().
    • Save and update without a page reload. For this we will need to look into nonce refreshing. See #7756.
    • Autosave in the browser revamp and improvements. Add some subtle, always present UI for restoring a post from in-browser autosave. Try to better detect when a restore may be needed (and show the current notice). See #36479.
    • Handling nested shortcodes. See #30094. I’m skeptical about this one, but please do let us know what your thoughts are if this interests you.
    • Save custom colours. See #31479.

    Under The Hood

    • Consider the new non-editable TinyMCE plugin for our non-editable views. See #36434.
    • Consider the TinyMCE API for inline toolbars, see #36480.
    • Responsive images for TinyMCE. See #36475. Depends on whether we will be saving the srcset and sizes attributes in post content, @joemcgill?
    • Handle inline image blobs in TinyMCE.
    • Different placeholders for more and nextpage tags. See #29804.
    • Auto embed bug. See #25387.

    Call for Contributors

    If you would like to see more of these features implemented sooner, join us. Everybody can contribute as designer, UX expert, developer, tester, the area you feel most comfortable with. Describing your workflow, how you use the editor, and what you find difficult or easy is also a very good way to contribute.

    You can also leave feedback on the relevant tickets.

    Let us know if you have more suggestions or ideas to add to the list.

    The next chat will be Wednesday, 13 April, 18:00 UTC in #core-editor.

    Andrew and Ella

    • WP Sites - Brad Dalton 7:33 am on April 13, 2016 Permalink | Log in to Reply

      Use of pre and code tags in the text editor. At the moment, you need to switch to the visual editor so anyone who has disbaled the visual editor and wrapped opening and closing PHP tags in code or pre tags, will find the code doesn’t display.

    • Martin Stehle 8:05 am on April 13, 2016 Permalink | Log in to Reply

      About Curly Quotes: there is a gap between the typography rules and the keyboard layout: missing keys to set the correct quotation marks.

      E.g. in german a cited sentence is bordered with „…“ but there is no key for that on a german keyboard layout: So you have to use the wrong "…" instead.

      It would be great if the editor corrects the quotation marks automatically based on the website language. About world wide standards of quotation marks: https://en.wikipedia.org/wiki/Quotation_mark#Summary_table

    • programmin 3:15 pm on April 13, 2016 Permalink | Log in to Reply

      By “inline toolbar” are you referring to support for TinyMCE inline mode (iframe-less) using contenteditable=”true” instead of an iframe, as in https://www.tinymce.com/docs/demo/inline/? That would be super useful to themes that want editor on frontend, inheriting all styles that they should be inheriting from the page. Is this inline live editing something you are planning on for default wp, similar to how the customizer lets you live-edit the theme settings?

    • Ahmad Awais 6:36 pm on April 13, 2016 Permalink | Log in to Reply

      Looking forward to these changes. Would love to contribute.

    • Ipstenu (Mika Epstein) 9:45 pm on April 13, 2016 Permalink | Log in to Reply

      I would take nested shortcodes off the list, given the rabbit hole that is shortcodes in general right now. That’s a project in and of itself :/

    • aidanlane 1:58 am on April 14, 2016 Permalink | Log in to Reply

      +1 for:
      meta box revamp
      Save and update without a page reload
      Autosave in the browser revamp and improvements – **currently not clear enough that they are happening or not**


    • LucP 9:34 pm on April 20, 2016 Permalink | Log in to Reply

      Hi! Wanted to hook into this conversation, as it might be interesting to also include this:

      Currently the publishing flow is still lacking some clarity. I’ve asked around and a whole lot of people still (instinctively) make the mistake of pushing “publish” when they meant to save a new copy of the draft.

      Especially if you have plugins enabled that auto-push posts to social media this can be a hassle. I know there’s keyboard shortcuts but that’s hardly an interface for the average user.

      If you’re rethinking Save, update and the general publish flow, i’d definitely like to help out!

  • Ella van Dorpe 6:15 pm on April 4, 2016 Permalink
    Tags: , editor   

    Editor chat 4.6 

    This Wednesday, 6 April, 18:00 UTC we’ll have our weekly editor chat in #core-editor. This time we’d like to discuss the roadmap and ideas for 4.6, so please join us if you can and are interested in pushing the editor forward. If you can’t attend feel free to comment here, or on the summary of the chat that we will post on this blog afterwards.

  • Ella van Dorpe 8:41 pm on March 28, 2016 Permalink
    Tags: , , editor   

    The Editor in WordPress 4.5 

    Inline Link Toolbar

    From WordPress 4.5 you will be able to link text with an inline toolbar, which replaces the link modal. You will still be able to access the modal with the gear icon in the toolbar, if you’re using one of the advanced fields or are using a plugin that extends the modal. Eventually we will try to move all those fields inline, though still under an advanced toggle and not visible by default. For those interested, see #36312.

    Inline link toolbar.

    Text Patterns

    We also added some more text patterns, or shortcuts if you like: `text` will change to <code>text</code> and --- (or more dashes) will change to <hr> while typing. We considered adding patterns for bold and italic, but there was no consensus yet and we’d like to test the inline text patterns first on an HTML tag mostly used by developers. See #33301.

    • Aaron Jorbin 9:00 pm on March 28, 2016 Permalink | Log in to Reply

      Are there any hooks to modify either the text patterns or inline link toolbar? How about for controlling the links list in the inline link? Is it possible to add information such as the post format to that list?

    • Peter Luit 6:41 am on March 29, 2016 Permalink | Log in to Reply

      Please, I already asked it before, just add the ‘open in new window’ option right in this inline toolbar, so without having to go to the normal link options……

      • Ella Iseulde Van Dorpe 10:04 am on March 29, 2016 Permalink | Log in to Reply

        Why would you like this option? We don’t encourage this as it changes default browser behaviour. It should be up to the user to choose whether to open in a new window/tab or not. With this attribute you are forcing it. I know there are some cases where it maybe could be a good idea, but definitely not enough to display the option in the inline toolbar.

        • Ipstenu (Mika Epstein) 4:37 pm on March 29, 2016 Permalink | Log in to Reply

          Would it be possible to have some filter set it to show by default? So it’s hidden, but if people like Peter ‘need’ it for whatever reason, they can force it to display?

          Obviously that would be a future enhancement.

        • ginowhitaker 4:11 pm on April 28, 2016 Permalink | Log in to Reply

          You must be kidding. Every website I’ve built using WP has needed links that open in a new window. Whether it’s as simple as a quick external reference, but you don’t want to lose your place on a page, or because of legal reasons,target=” _blank” is used a lot. Clients request this all the time.

        • adrieet 11:44 am on May 9, 2016 Permalink | Log in to Reply

          Not sure how to put this: BUT its not your place to tell Millions of Bloggers how to use their external Links by destroying simple functions. If someone wants to make Links open in a new Tab or new Window then then it should be possible. Also please check how many people have installed plugins to set external Links to Nofollow. All this simple functions are made much more difficult and unreliable, with this user unfriendly in line thing. I need 5 tries to set every fu..ing link now. To set a new link or check if a link is set correctly you have to click on the Link thing and then go back to the text and click on the open link editor sh.t. If you added a link in the “in line field” and then click on the “link options” the Link is deleted! Do you discourage Links in general?

      • Aaron Jorbin 5:10 pm on March 29, 2016 Permalink | Log in to Reply

        Using target=”_blank” (which is used to open in a new window) is often an anti-pattern and there are very few valid use cases for it. It takes away control from the reader, breaks the back button, and is “like a vacuum cleaner sales person who starts a visit by emptying an ash tray on the customer’s carpet”[1].

        Here is some reading on the subject:

        1) https://www.nngroup.com/articles/top-10-mistakes-web-design/

      • Evan Herman 8:59 pm on March 30, 2016 Permalink | Log in to Reply

        Just write a plugin and add the button yourself. Probably 30 or so lines of code to get it done.

      • bactisme 9:18 am on April 18, 2016 Permalink | Log in to Reply

        I too really would like to see that append. Same for nofollow.

    • Primoz Cigler 4:16 pm on March 29, 2016 Permalink | Log in to Reply

      Excellent for more text patterns!

    • Rask 7:03 pm on March 29, 2016 Permalink | Log in to Reply

      > We considered adding patterns for bold and italic, but there was no consensus yet and we’d like to test the inline text patterns first on an HTML tag mostly used by developers.

      I’d say most people would be just fine with the Markdown asterisks and underscores for emphasis elements (bold and italic). E.g. _this is italic_ and *this is bold*. Just like `code uses backticks` in Markdown.

      Now that I think of it we could create a profile system for various formatting shortcuts like IDEs and other software offer profiles for hotkeys? This way people could turn them off, or take a pick from “common” choices, one being Markdown for instance. People can disable the visual editor presently too.

      Some time ago I voiced support for Markdown support in the editor feature wishlist, but that was taken down quite instantly. Glad to see Markdown influenced formatting making its way to the editor now. 🙂

    • malkah 7:12 am on April 14, 2016 Permalink | Log in to Reply

      is it possible to go back to the old link modal. its so much better.

      • Ella Iseulde Van Dorpe 8:21 am on April 14, 2016 Permalink | Log in to Reply

        What part did you find better?

        • Sapphire 8:24 pm on July 16, 2016 Permalink | Log in to Reply

          I’ll answer that. With this one, it takes more button clicks to get to the window where I can set target_blank, and regardless of what you say, it is expected now with mobile (because the user can’t easily open links in a new tab, and typically they want to). With this one, it has a glitch where sometimes the little inline window won’t go away unless you click something else, click the link button, and click the unlink button. This is a nightmare when creating link roundup posts, which many bloggers do on a weekly basis. Also, in many cases, when I go into the old link modal to set options, it sometimes shows not the current link text I’m working with and have highlighted, but the last link text I finished working with. Thus forcing me to retype the link text in the window.

          This is a neat idea, but it introduced so many more problems than solutions for many of us.

        • cassihl 1:17 pm on July 18, 2016 Permalink | Log in to Reply

          Yes, please implement a way to go back to the old link modal. The new way is more confusing to teach to clients. It’s more straightforward what you are supposed to do in the old modal.

    • SebastiaanO 7:23 pm on April 14, 2016 Permalink | Log in to Reply

      I think this addition is an improvement. Currently, the custom added editors I added in a plugin are not handling the links anymore, resulting in a js error. Any tips on how to load custom TinyMCE editors in WP 4.5?
      Maybe use another button for “link” in the toolbar? (see snippet below – using the tinyMCE file in the wp-includes dir).

      plugins: “paste,wplink,visualblocks,code,charmap”,
      height: height,
      menubar: false,
      block_formats: “Paragraph=p;Header 1=h1;Header 2=h2;Header 3=h3;Header 4=h4;”,
      toolbar: “formatselect,bold,italic,underline,link,unlink,bullist,numlist,visualblocks,code,charmap,pastetext,removeformat”

      • SebastiaanO 7:42 pm on April 14, 2016 Permalink | Log in to Reply

        Fixed: When loading a custom TinyMCE editor, now also configure to load the “wordpress” plugin to inherit the new functionality (or have a link button that won’t work).

    • tssblog2016 6:51 pm on April 20, 2016 Permalink | Log in to Reply

      I tried inserting a link into a post and it’s not showing up. What am I doing wrong

    • mashupmom 4:16 pm on April 23, 2016 Permalink | Log in to Reply

      I also would love a way to revert to the old link editor — this change is messing with my workflow. The inline editor will not disappear in Chrome and obscures text after I create a link. It’s now extra clicking and steps to open up the full link editor to make a link nofollow. I used to just be able to highlight, add link, paste link, close, and now have multiple extra clicks and steps — this adds up when you need to add multiple links.

    • Nevis-1 1:14 pm on April 25, 2016 Permalink | Log in to Reply

      Bring back the old link editor, the new one sucks.

    • rickcurran 3:27 pm on April 26, 2016 Permalink | Log in to Reply

      I am seeing problems with the new link editor simply because of the choice of icons used. Clients are clicking the X icon thinking that this is how to close the inline link editor but instead this removes the link.

      It would seem much more consistent to use the same “Insert/Edit link” and “Remove link” icons that the main toolbar uses, rather than the pencil and X icons. Doing this would make it more obvious as to the function of these buttons as users are already familiar with the existing icons for adding and removing links.

    • jchew 12:09 am on May 3, 2016 Permalink | Log in to Reply

      I am having an issue with initializing the inline link toolbar in a custom instance of the WP editor.

      The instance is added in a dynamically loaded modal using the wp_editor function and some JavaScript. It has been working correctly up to WordPress 4.5, but is now broken.

      There are some parts that work. When I click the button to add/edit a link, the text does get highlighted as a placeholder, it’s just that the toolbar does not show. The markup for the TinyMCE plugins does get added to the bottom of the document and if I open and close the media editor attached to the new instance, the inline link toolbar will then function correctly.

      There are no JavaScript errors when the toolbar is not functioning correctly, it just doesn’t seem as if the JavaScript handlers are bound correctly or something.

      This is a bit of a weird one, but I would super appreciate any help or advice that anyone might have.

      Here is the JS code I use to initialize the WP editor instance.

      var $element = jQuery('#newcontent');
      var qt;
      var textfield_id = $element.attr('id');
      window.tinyMCEPreInit.mceInit[textfield_id] = _.extend({}, tinyMCEPreInit.mceInit['content']);
      if(_.isUndefined(tinyMCEPreInit.qtInit[textfield_id])) {
          window.tinyMCEPreInit.qtInit[textfield_id] = _.extend({}, tinyMCEPreInit.qtInit['replycontent'], {id: textfield_id})
      qt = quicktags( window.tinyMCEPreInit.qtInit[textfield_id] );
      //make compatable with TinyMCE 4 which is used starting with WordPress 3.9
      if (tinymce.majorVersion === "4") {
          tinymce.execCommand( 'mceAddEditor', false, textfield_id );
      window.switchEditors.go(textfield_id, 'tinymce');
      //focus on this RTE
      window.wpActiveEditor = textfield_id;
      • jchew 4:15 pm on May 5, 2016 Permalink | Log in to Reply

        An update, this issue does appear to be tied in with the Bootstrap modal in which I am adding the instance of wp_editor.

        I am not sure what about opening and closing the WordPress media modal makes this come un-stuck. I have tried manually re-focusing on the wpbody-content ID when the modal / editor is initialized using the following code, but that did not work.


      • jchew 8:58 pm on May 5, 2016 Permalink | Log in to Reply

        Solved.. it turns out the link dialog does not work if the body has the “modal-open” class.

    • adrieet 11:49 am on May 9, 2016 Permalink | Log in to Reply

      Can you please tell me how to get the old “user friendly” add link function? The Inline thing is not working most of the time and its much overblown and unusefull. I want many links to open in new tabs and to be nofollow. Before it was much easier. Just click on add link, copy the URL in and add the checkmarks for open in new window and nofollow. Now you have to find the spot where “inline link” thing is and click on the link options. Then it shows me a messy list of pages and blog posts “wtf”. If I add a URL in the in-line and then want to edit the options, the link is deleted.

    • rosebakes 6:31 am on May 24, 2016 Permalink | Log in to Reply

      I do not like the new inline link function at all. I prefer to have the option to open in a new window and add “no follow” without having to click 3 or 4 times. I understand that it’s your opinion that “open in a new window” shouldn’t be forced, but as a reader/user, I prefer it on EVERY website I use and I’ve never had a single complaint on my blog. Besides, the new link editor makes adding links take so much longer with multiple clicks to make the changes I want. Also the inline window will not go away or always display next to the link I’m editing – it’s very glitchy. I think those of use who prefer the options to open up immediately should have it. It’s really disrupting my writing process. Is there a way to go back to the old one? I hate this update!

    • Nico Martin 9:43 am on May 25, 2016 Permalink | Log in to Reply

      Hy there I just released a Plugin, that might solve all your problems:

      Advanced WPLink

      With this plugin you are able to enable/disable the inline link. Besides that it gives you the possibility to add a rel=”nofollow” tag and some stylings.

  • Andrew Ozz 11:22 pm on March 8, 2016 Permalink
    Tags: , , editor   

    Link modal (wpLink) changes in WordPress 4.5 

    There is a new and improved inline links dialog in the Visual Editor, see #33301. When the users type in the URL field, it uses jQuery UI Autocomplete to search for local posts and pages.

    The old modal dialog (a.k.a. wpLink) is still used for “Advanced” link options. It was simplified, the infinite scrolling bottom part was removed. Now this dialog also uses UI Autocomplete on the URL field to search for posts and pages. That makes it consistent with the inline dialog and leaves more space for plugins that want to add additional settings in it.

    If your plugin uses or extends wpLink, please test it now to confirm all is working properly.

    • Mike Schinkel 2:34 am on March 9, 2016 Permalink | Log in to Reply

      @azaozz Nice work!

    • swinggraphics 4:00 pm on March 10, 2016 Permalink | Log in to Reply

      Was this a highly requested feature? The complaints I have and those I talk to about links in WP are never that the interface needs a tweak, but that URIs (pretty much everywhere, like media) need to be protocol-independent and relative rather than absolute (or with placeholder for site id in a network).

    • Peter Cralen 4:17 pm on March 12, 2016 Permalink | Log in to Reply

      Great enhancement, thank you.

      A common task for links is set up also the target – Open link in a new tab. It would be helpful if there is also little check box (maybe with some icon) to do this task without needs to open old modal dialog.

      After this new inline dialog, setting a target is harder than before, it requires one extra click, and it opens another modal. If something has to be easier, it’s not necessary to do another thing harder for users.
      I think there is enough space inside that inline modal dialog for this check box.
      In this case, maybe old modal box could be removed completely in near future.

    • Torgut 9:29 am on April 15, 2016 Permalink | Log in to Reply

      My number one priority regarding WordPress is not find a way to get rid of this Link Modal change. I can’t work with this new concept. For me it’s basically absurd. It’s the first time I have a hard time understanding a change in WordPress. Probably it will mean a new plugin, which I wouldn’t need if not to correct the situation.

      • Pascal Birchler 10:33 am on April 15, 2016 Permalink | Log in to Reply

        Can you elaborate on why it is “absurd”? I have only heard good things about the new inline link dialog so far and I’m sure we all would love to hear what can be improved.

        • dkatiepowellart 12:47 pm on April 25, 2016 Permalink | Log in to Reply

          It isn’t a matter of learning to adopt the feature —
          I’ve had to do this ridiculous thing 4-5 times on each post —
          I figured it out — but how stupid is this change to what was a simple tool?
          It used to be when you were writing you chose ONCE to have your links open in
          a new page (Two clicks) then clicked ONCE and popped the url in and wa-lah, there it was, already set to open in a different window.
          Unless you saved or exited, it remembered you wanted your url links set to open in a different page.
          Now, the person (or omigod do not tell me this was a group decision to fix what was not broken) who created the “shortcut” which is NOT a shortcut unless you want to drive your readers to another site which is BTW stupid —
          makes us click THREE times
          EACH TIME to have our link open in a new window…
          So if I have 4 links, it used to be I clicked 6 times.
          NOW I click 12 times.

          Stop fixing things which are not broken.
          Get rid of this absurdity.

        • dkatiepowellart 5:18 pm on May 9, 2016 Permalink | Log in to Reply


          That should explain it. Although it seems no one here is looking.

  • Ella van Dorpe 8:46 pm on January 16, 2016 Permalink
    Tags: , editor   

    Editor wish list for 4.5 

  • Ella van Dorpe 6:42 pm on November 3, 2015 Permalink
    Tags: editor   

    Weekly editor chat resumed 

    After some quiet time in #core-editor, we’d like to resume the weekly editor chats. The next one will be before the weekly developer meeting on Wednesday, 4 November 2015, 18:00 UTC. It will be used to discuss new features, answer questions, and do component bug scrub if there is time. See you Wednesday!

  • Ella van Dorpe 8:54 am on August 1, 2015 Permalink
    Tags: , , editor   

    Editor Enhancements in 4.3 

    Text Patterns

    We added a small set of text patterns, or text shortcuts if you will. These will hopefully keep you focussed better on your writing and save you some time. 🙂

    Typing *  or -  will automatically give you a proper HTML list right away. Same for 1.  or  1) , but then ordered. Not your intention? Pressing backspace will undo this change. You can also use the undo button, ctrl/cmd+z or esc.

    Starting your paragraph with two to six number signs # will convert that paragraph to a heading. Similarly the greater-than symbol > will convert the paragraph to a blockquote.

    We’re planning to add some more next release, and a way for plugins to extend this.

    Here’s a demo video @boren made.

    Inline Link Toolbar

    This toolbar will show up when you put your cursor in a link. You’ll now be able to see a short version of the URL without having to open the link modal all the time. Clicking it will open the page that it links to in a new browser tab. If you wanted to do this before, you had to open the link modal and copy paste the URL in a new browser tab yourself.

    It also comes with an edit and remove button. We hope to move the editing experience inline next release as well.

    Inline link toolbar

    • Bjørn Johansen 8:25 am on August 5, 2015 Permalink | Log in to Reply

      I think this is pretty sweet.

      However, in some locales, this will at one point cause an issue when someone tries to start a paragraph with a date that is the first day of a month. At least here in Norway we write dates as e.g. “1. september” where the dot means “1st”.

      • Bjørn Johansen 8:28 am on August 5, 2015 Permalink | Log in to Reply

        Sorry for commenting before thinking. This is where the undo functionality becomes very handy.

        • John Blackbourn 1:38 pm on August 5, 2015 Permalink | Log in to Reply

          Valid point, Bjørn. Hopefully the combination of being able to press backspace, undo, esc, or cmd/ctrl+z will mean that anyone who does end up with an unexpected list, blockquote, etc will be able to back out of it one way or another.

    • Fernando Tellado 3:52 pm on August 5, 2015 Permalink | Log in to Reply

      I’ve found a bug with links. When you try to change an image link inserted in the editor to another one link from the chain (link) icon in the editor the image disappear. I think this is a bug related to the new inline link editor ’cause it has appeared after its introduction

    • Lara Littlefield 2:56 pm on August 10, 2015 Permalink | Log in to Reply

      I am so excited about these editor ✨ enhancements. This is a huge help for mobile and alternate device/UI composing and editing.

    • Jeff Chandler 9:32 pm on August 17, 2015 Permalink | Log in to Reply

      Why is this video not embeddable/shareable?

    • frameitsam 4:54 pm on August 22, 2015 Permalink | Log in to Reply

      This is all good and well, but what happened to the “edit” and “remove” buttons when you select an image in the editor? These handy functions seem to have disabled the image editing functions.

  • Ella van Dorpe 9:26 pm on July 29, 2015 Permalink
    Tags: , , editor   

    Old Distraction Free Writing Code Removed in 4.3 

    This release we removed all old DFW code, which hasn’t been used in core since 4.1. We left it in core for two releases so plugin authors had the time to update. If it is essential to your plugin, the files in 4.2 can still be reused and improved. See [32677].

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar