184

TL;DR: We are testing our new open source Stacks editor that offers both Markdown and rich text input options. If you’re interested in testing it out and giving us feedback, you can opt in by visiting your preferences page and enabling the Stacks Editor. You can opt out at any time but it will take up to 10 minutes to revert to the old editor. Note, the new editor will only be active when drafting or editing answers on MSE or MSO during the alpha test.


About six months ago, our product teams and Community team began exploring whether we could bring to our public sites the Stacks rich text post editor that launched on Stack Overflow for Teams (or Teams) over the summer. We’ve been spending that time discussing the needs internally and also talking with some of our most highly-engaged users about the new editor - our Moderators and members of the Charcoal group - to understand what might need to change or be included to make using the new editor an easy change-over from the old editor.

Through this process, we’ve received dozens of answers with ideas for improvements, bugs that needed to be squashed, and UX confusion that needed to be ironed out. We’ve addressed many of the concerns these two groups mentioned and are ready to bring it to the larger community through an opt-in alpha test on MSE and MSO. We are asking for your constructive feedback to see where there’s room for improvement to make it into a tool both people who are comfortable with Markdown and those who may be more comfortable with rich text can use successfully.

Here's what the two views look like - you can click to view a larger image:

Screenshot of the new editor window in Markdown mode with the text of this post input the text is monospaced and the Markdown in the post is visible, though sections in bold appear bold Screenshot of the new editor window in rich text mode with the text of this post input. The post is in Arial with bold and headers and horizontal rules being visible rather than the Markdown.

The test

The goal of this alpha test is to get an initial understanding of how well this new editor would be received and to also discover any concerns that would break workflows for users who like the current editor or prefer to work in Markdown. We also want to consider users who may not be familiar with Markdown, too, as they make up many of the users on our non-technical sites. This is the first public phase in a process where we hope to fully test and refine the editor so that, when it launches network-wide, people will find it easy to use and to be a major improvement over the current editor.

We understand that rich text entry is a difficult thing to get right and realize that it may take several months to find the right solutions before we can make this live network-wide - and that comes with the understanding that there may be unsurmountable issues - but we feel that working through this process with y’all will, at minimum, help improve the new editor experience on Teams and may end up with a great new editor for everyone to use.

This is part of a multi-part test that will look something like this:

  • Initial release on Teams with feedback from highly-engaged users (e.g. Moderators) (Completed Summer 2020). The goal of this was to get feedback and get a good idea of how much we need to change the editor so that it will work for our public platform community. This allowed us to test many (though not all) of the features with a small group of people without impacting the public site.
  • Testing on MSE and MSO through an opt-in alpha test. The goal here is to further refine and identify solutions that will help the new editor be openly adopted by users, primarily active members of the community.
  • Usability testing sessions with users of several different experience levels. The goal here is to make sure that the features and UX we create after responding to our highly-engaged users is still transparent to others. We’ll watch how users of varying experience levels interact with the editor to identify and make additional improvements with the goal of an intuitive user experience that has sufficient guidance where needed.

As to a timeline, this is expected to take a while to work through. One of the benefits of the alpha test is that people can enable and disable it as they wish. For the rest of 2021 Q1, our plan is to leave the test running so that y’all can try it out in a more long-term way if you wish. While we’ll be fixing major bugs, we won’t be prioritizing new features or adjustments until we start digging into your feedback from this test and the feedback from the usability sessions in the second quarter of 2021. See a bit more on this in the giving feedback section below.

Assuming these tests go well and we find solutions that make post creation and editing easier than the current system, we’ll move into a gradual rollout phase, starting again with MSE and MSO and then to the sites with standard editing tools, reserving the sites with specialized editor add-ons for the end so that we can make sure that their tools work correctly upon launch.


Why are we working to bring a rich text editor to our sites?

While there have been some requests for a rich text entry option over the years (this one going all the way back to 2009), there’s never been much support for them from users - in fact, many of the requests get strong disagreement from other users. Markdown is a great tool and many users are or have grown accustomed to it - I admit to regularly trying to use Markdown in rich text spaces. That said, many of these requests have been to replace Markdown with rich text and that’s not something we want to do.

As a platform that is largely used by programmers, Markdown is generally a familiar format for many and they’re very comfortable using it, particularly now that we follow the CommonMark standards. For those who don’t know Markdown, we’ve expected them to learn and we give them some assistance but, in many cases, posts end up poorly formatted and need participation from the community to improve. Many of my edits on English Language Learners are purely to improve post formatting.

Additionally, our editor has been around since the beginning with few improvements in that time, so a major upgrade is in order and, in looking forward, we feel that a redesigned editor using Stacks will be more easily maintained and improved as we go forward.

Teams needed a rich text option

We have a great team who works to enhance the Teams product to meet the needs of companies and organizations who are using it for internal knowledge sharing. One frequent pain point from these users was the lack of a rich text editor - here’s a statement from Ham, one of the Teams developers:

We started building the new Stacks Editor as a response to feedback from our Stack Overflow for Teams customers. While Markdown has become a widespread and successful format for writing content - not only at Stack Exchange but across the web - some of our Teams customers told us that they’re not comfortable writing their content in Markdown. They didn’t know the syntax and faced a learning curve before they could start writing the way they wanted to. Writing questions and answers wasn’t as easy as they were used to from other places. For us it’s important to make contributing as easy as possible. Writing questions and answers should feel natural and come without a lot of friction.

This makes sense. Copy and pasting from a rich text editor like Google Docs or Word is much more common within a company where you may be transferring information from existing documentation to a Team, whereas much of our public site content is created from scratch. That said, it’s not unheard of to copy content in the form of quotes into posts, where a rich text detection feature would be helpful so that adding the Markdown manually wasn’t necessary.

The main driving force for the development of the new editor was to improve the experience of Teams for our existing users and give it a feature set that would attract additional users. That said, since many of the people using Teams are developer-centric groups, they also are often comfortable with Markdown, so we wanted to ensure that both options were available. More from Ham:

The new Stacks Editor tries to be the best of both worlds. If you’re happy with writing Markdown and liked the way the old editor helped you with that, the new editor will feel very familiar. You can write Markdown, use familiar keyboard shortcuts, upload images and more. If Markdown is not your strong suit, Stacks Editor allows you to switch over to the new rich text mode that allows you to write in a more WYSIWYG kind of fashion.

We still think that Markdown is the way to go, but we also see the benefits of a rich text editor for less technical users and/or network sites who may be more accustomed to a WYSIWYG style editing. With the new Stacks Editor, Markdown continues to be the leading format for your content and everything you write will be transformed and stored as Markdown at the end of the day.

So, our focus in building the new editor was to add the option of rich text but still maintain a Markdown focus because we love Markdown and think it’s a great experience for those who already know how to use it and is relatively simple to learn but we also want to simplify or improve the experience for people who may be copy-pasting into posts or who don’t know Markdown.

More than just rich text, we’re simplifying future work for development

The current editor has been around since 2008 and, while we’ve made changes along the way, it’s largely unchanged and now makes building new features difficult. Additionally, by adopting and improving the Teams editor on our public network, we’re simplifying future work on ask, answer and edit pages and maintaining similar features between Teams and the network. My final quote from Ham:

Our old editor has served us well for many years, but due to a number of issues (reverse-engineered code that is hard to work with, inadequate API for handling cross-browser issues, and bare-bones content-editable support) we are unable to use it as the base for any major upgrades. Additionally, there are many advantages from basing an editor on a modern foundation (like we have done here on top of prosemirror), which can take care of many of the nasty "content-editable" concerns and keep things safer and more cross-browser compatible.

Being around for so long, it has accumulated quite some cruft and has become hard to maintain and evolve the way we would love to. Over the past years we tried revamping the editor a couple of times only to find out that it would be too hard to do. When we started building the new editor for Teams, we knew this would be a good opportunity to greenfield a new editor overhaul that would ultimately benefit all our users across the network.

On top of this, we’re opening the editor up for everyone to use and contribute to. Like Stacks, the new editor is open sourced, so if you’re interested in how it’s built or want to contribute to improving it, you can find it on the Stacks-Editor repo.

Building editors is hard - particularly when dealing with rich text

I’ve learned the quirks of a variety of different editors over the years, whether it was BBCode on the forums I participated in, Wikitext on MediaWikis, Markdown here on Stack Exchange, or any of the various rich text or hybrid editors on the various platforms I’ve used (e.g. Jira, FreshDesk)… so I’m comfortable adapting to new styles, but I also find that some editors make assumptions that frustrate and confuse me and make me not want to use them any more. We want to avoid this frustration!

Because our focus is on Markdown, with the addition of special formatting for tables and spoilers, we’re able to limit what our rich text editor has to do - we’re not increasing which formatting options are available (e.g. colorful text or underlines) which is one way we’re working to keep our rich text implementation and the conversion between rich text and Markdown simple, easy-to-understand, and as frustration-free as we can.

The major changes

Other than the optional rich-text entry, there are a bunch of other changes, big and small, that you’ll see in this test. Below are some of the biggest ones including a brief overview of how rich text entry works. A lot of what’s written below was penned by Ben Kelly, who’s done a lot of work with Ham to get this editor going and is supremely knowledgeable of the features, so big thanks to him for that!

Rich text mode

This editing mode was designed to largely resemble traditional word processing software that many users are used to. However, we've added in some extra features:

  • Markdown-style "input rules" for block level syntax
    • Typing # , ## , etc creates a header; typing > creates a quote; * creates a list, and so on
    • We’ve got inline input rules (bold, italics, inline code, etc.) on a list of things to investigate for a future release
  • Link and image editing tools will allow editing link URLs for links and the addition of an image description and title for images.
  • Intelligent copy/paste support - Pasting external content from e.g. Google Docs or code from your editor of choice will retain most of its existing formatting, provided that formatting is in Markdown.

Ultimately, the rich text editor is converted back to Markdown and should support everything you can do in Markdown, with some caveats:

  • Pasting rich text from outside sources isn't perfect, especially with very complicated content
  • What we can support in rich text mode is restricted by our backing Markdown implementation, so things like merged cells in tables or super/subscript aren’t supported, even when we do support the HTML (see next bullet).
    • This is really more of a feature than a drawback. We <3 Markdown and are committed to supporting it first-class for the foreseeable future
  • HTML support is HARD. We make no promises that any HTML written in Markdown mode will be editable in rich text mode
    • We recommend using the equivalent commonmark syntax when available. We’re looking to extend our supported Markdown syntax so users won't need to type HTML anymore.
    • Don't ask why HTML is hard. It's a long story that could be a blog post of its own.

The Markdown - rich text switcher

Two screenshots in one - on top, the Markdown switcher in Markdown mode with the switch background green and the selector on the right; on the bottom, the Markdown switcher in rich text mode with the background grey and the selector on the left.

To allow for movement between rich text and Markdown modes, we’ve added a switch. When the dot is on the right (green background), you’re in Markdown mode; on the left (grey background), you’re in rich text mode. The current default for all users is Markdown but, after you use the editor, the system will remember your last-used option as your default. So, if you submit a post or edit while in Markdown view, you’ll see that the next time you open the editor; if you do so in rich text, that will be the view you have when you next use it. The default configuration for users can be changed per-site, so if a site feels that rich text makes more sense as their default, we can allow for that.

Preview is collapsed into the rich text view

Over the years we’ve gotten lots of questions about whether we could optimize the preview so that it didn’t take up so much space on the screen. If you’ve ever written long posts, you may be familiar with the feeling of doing a lot of scrolling to get from the end of a preview back to the edit window. With the new editor, you see the preview by using the Markdown toggle to switch between Markdown and rich text modes and, because the rich text preview is part of the editor, you can edit right in the preview rather than having to find the edit window again. This is a lot more convenient for mobile users, too, with their smaller screens where scrolling through even a short post can mean a lot of work.

Aaron, our Principal Product Designer for Design systems explains the value of an editable preview:

We think this is more than a layout issue. We could put these previews side by side, or toggle between them like GitHub does, but I think having a preview at all is something we can move beyond. Tiny sidenote: I worked on GitHub’s editor in 2016! We could explore alternatives like having a button that launches a full screen preview, but I think that’s wasted effort when we could be writing directly in the preview experience.

The web has matured past the point of requiring Markdown syntax and discrete previews. Why should any text editing offer a read-only preview state in 2021? Is writing, previewing, noticing a mistake, and moving back to the editor truly better than simply being able to edit the text? Would you accept this interaction model in your word processor? In Notion? In Google Docs? In Medium?

We feel this is a positive change for these and many other reasons but we do understand that it’s a big departure from the current format. Please take some time to see how this new workflow feels and let us know what you think and how we can improve this. I know that many of the prior requests have been for a side-by-side preview to cater to the wider screens that many people have, particularly as this matches many other Markdown editors. Unfortunately, this can be complicated on smaller screens, which would require different placement and it’s pretty common to have previews separate from the entry form, like with GitHub’s two-tab format.

We do have a few known issues here:

  • While switching between modes does maintain your approximate scroll position, it doesn’t remember where your cursor was. Any time you switch, your cursor will move back to the top of the post rather than staying where you were.
  • There’s no history when switching modes, so flipping between views will cause you to lose the ability to undo/redo the changes from the other view.
  • Since the rich text preview will interpret your Markdown, any incorrect Markdown (MD) may be escaped out by the rich text editor. When you return to MD view, you will be able to fix these errors.

Syntax highlighting in Markdown mode

You’ll notice your Markdown experience is a bit less monotonous because it now responds to the Markdown you use by changing the text in the pane - headings will be larger, bold text will appear bold, as will italics, and links will be in blue and code will be in grey. I’ve found this really helpful in drafting posts as it identifies a lot of the Markdown errors I might have made, making it so I’m less likely to even need to look at the preview. This isn’t currently CommonMark compliant but we’re working on improving it.

Changes to formatting buttons

We’ve removed some buttons and added some new buttons to the ones available for formatting. Here’s what the formatting bar looks like now:

A screenshot of the post formatting bar showing the various buttons. In order from left to right there's the header button, bold, italic, inline code, links, quotes, block code formatting, image uploading, tables, ordered lists, unordered lists, horizontal rule, and a question mark for help. On the far right is the "Markdown" switch

Removed:

  • Undo/redo - these features still work with your standard key combinations but we’ve removed the buttons themselves - we’ve also improved undo/redo history support to be much more reliable overall.
  • Stack Snippets (temporary) - We couldn't get Snippets built into the initial alpha test, so if you need to add a snippet to a post, you'll need to disable the alpha to do so.

Updated / New:

  • Tables - this button will create a default three-row, two-column table and have special menu options when in rich text mode that allows adding/removing rows and columns.
    A screenshot of the formatting bar with the table tool open and the various options to remove and insert columns and rows visible
  • Headers - this button has been redesigned and moved to the first position.
  • Inline code / code blocks / Stack snippets buttons - one piece of feedback from our early tests was that for rich text, we need to differentiate between inline code and code blocks but on Teams we reused the same icon for code blocks that we currently use for Stack Snippets - to allow all three options, we created new icons. Snippets are disabled for the alpha but you can see the new trio of buttons (left to right - inline code, code blocks, snippets)
    The new icons for the code markup buttons - a pair of angled brackets "<>" with no background for inline code, a pair of angled brackets with a background for code blocks, and a pair of angled brackets in a stack of icons for snippets.

We're planning to add keyboard shortcuts to the formatting buttons but they aren't part of this initial alpha test.

Markdown mode is your go-to for fine-tuning posts

Markdown mode will give you fuller control of your posts, as it already does. Here are a few places you’ll want to stick to MD when composing or editing posts:

  • Adding a language to a code block for syntax highlighting purposes - while we’re looking to add this to rich text, for now it’ll require MD. The system will still auto-detect languages based on tags as it usually does but if you need to call out a specific language, you’ll need to use Markdown mode.
  • Markup that requires HTML - we still support some HTML in posts but the rich text mode won’t create it, so if you need to include HTML in your posts for formatting such as subscript or superscript, you’ll need to enter Markdown mode for this.
  • Spoilers - like HTML, they're supported but we don't have a button for it, so you'll need to use Markdown mode to add them.
  • Creating complex lists - this is possible in rich text mode, but it’s not as intuitive as using Markdown, particularly in special cases such as lists with indented code blocks.
  • Fine-tuning images - resizing or adding links to sources or full-sized images will need Markdown mode.

Inline text and image links are the norm

The image and link tools will now add images and links inline rather than in the bibliography format. While the latter will still work, you’ll have to create it manually. Right now, images don’t have their image plus link formatting but we’re working on getting that added in a future release.

How to participate

Screenshot of the user preferences page with the alpha test opt in option circled.

If you’d like to opt-in to the alpha test, visit your preferences page and opt in by enabling the Stacks Editor opt in option. At the outset the new editor will only be available on answers - you won’t see it on questions, profile pages, tag editing pages or any other editing forms around the site. Opting in is global, so if you opt in on MSE, you’ll also see the new editor if you’re on MSO. If you decide you’d like to opt out, you can do so in the same way, switching the slider on your preferences, though it may take up to ten minutes for the editors to return to normal.

Giving feedback

This feedback phase is an incredibly important part of this process so we really appreciate any of you who take the time to try the editor out. If you run into bugs, usability issues or if you think of features that would improve your experience with the new editor, please leave an answer here - one per answer - so that we can review and respond to each. Steps to reliably reproduce are always appreciated along with which browser/s you're experiencing the bug in, and especially so when it comes to obscure edge cases or subtle usability issues. Additionally, because this project is open sourced, for truly technical bugs, you can file them as an issue on the GitHub repo - if you feel comfortable with that - if we get reports filed in both places, we’ll link them.

Our plan is to transfer issues from our internal system to the GitHub repository and add any new ones that come up here so that anyone who’s interested can see what we’re working on and how we’re prioritizing this work.

While it’s great to hear your overall thoughts about the editor, if there’s too much in one post it can make responding difficult so try to keep each answer relatively concise. You’ll have until the end of the alpha to add the answers here. Once it’s over, we’ll let you know how best to give feedback.

Thanks

This project couldn’t have been possible without the work of so many people and they all deserve a ton of credit. In particular I’d like to recognize Ben Kelly, Ham Vocke, Aaron Shekey, Des Darilek and Adam Lear for all of the effort that they’ve put in. Additionally, to those who have taken the time to test and give feedback while the editor was in Teams only, thank you!

45
  • 7
    I like this editor, I've been using it in SO for Teams for a while now. Tooltips are great. And thank you for giving us an option. – Ollie Jan 26 at 19:32
  • 5
    This post is getting more answers than upvotes. Popular, you think? – Ollie Jan 26 at 20:41
  • 7
    @Ollie sorry, my fault. I can only upvote it once... – Glorfindel Jan 26 at 21:13
  • 62
    "in many cases, posts end up poorly formatted" - I doubt that's the fault of markdown. Many askers are just too lazy to apply formatting or grammar. – Bergi Jan 27 at 0:14
  • 37
    @Bergi I mean... that's a possibility... but I really don't think that everyone, network-wide, who fails to perfectly format posts are all just lazy. And, honestly, it's kinda uncharitable to assume that. I'd much rather give people more options to make their post look great and honor that's at least part of the problem. – Catija Jan 27 at 0:55
  • 4
    Watch the terminology around this. Searching for "Stacks Editor" in Google comes up with StackEdit, which isn't built by Stack Exchange. (Incidentally, it seems to be a much more feature-rich markdown editor which also solves many of the problems users have shared in answers below. Play around here) – Robotnik Jan 27 at 4:52
  • 27
    On the sites which have mathjax enabled, the MathJax source will be shown in both views, right? Or does the rich text view actually show rendered MathJax? – Martin Jan 27 at 6:56
  • 7
    @Robotnik we've come full circle. If you check out StackEdit's GitHub repo you can see how they built it on Stack Overflow's previous markdown engine. Personally, I'm not worried about the name. Ultimately, it's gonna become the editor component in our Stacks design system so people can find it there if they're looking for it. – Ham Vocke Jan 27 at 8:35
  • 4
    How about you use the official sandbox post for that @ouflak – Luuklag Jan 27 at 13:51
  • 11
    "Why should any text editing offer a read-only preview state in 2021?" - arguably, WYSIABNQEUWYG editors that a lot of old forums had and that universally failed at anything more complicated than bold, italic and underline are exactly what the Internet has been moving away from. – Maciej Stachowski Jan 28 at 7:37
  • 45
    @Catija "I think having a preview at all is something we can move beyond" Please, please no. Especially if there's still bugs to work out that wreck your formatting, nixing preview should be a nonstarter. – TylerH Jan 28 at 22:54
  • 6
    @TylerH: I know what it is. It is a UI catastrophe. Every place that uses them generally also includes some additional means to try and make clear whether left or right means the feature is activated. Look how much text was spent in describing the feature that went into describing how to turn it on and off. Notice that it also changes color to help make clear when it is on. Compare that to an unambiguous check box that needs no explanation. The sliders suck. – JRE Jan 29 at 6:40
  • 8
    @JRE .... So post a passionate posted about why a checkbox would be better rather than having your point of view forgotten, mouldering in the comments. The whole point of this is to try to get these things sorted out – Journeyman Geek Jan 29 at 12:01
  • 25
    Chiming in with others. This must be site specific. Killing the preview will introduce difficulties in Math.SE and other MathJax -using sites. I might manage myself, but others needing more complicated formulas and such are seriously hampered. I am also very worried about our new users who have not written thousands of pages of LaTeX like I have. They need the help of a preview pane. Typically they start with simpler pieces when the need to scroll much is not so pressing. – Jyrki - No Shog9 - No SE Feb 2 at 19:36
  • 4
    @T.J.Crowder It's not active on SO, only on MSO and MSE. :) To answer your specific question, no, there's no limit. – Catija Feb 10 at 13:58

105 Answers 105

1 2 3
4
4

SHIFT + PAGE UP does not select the entire text when Markdown is switched off. E.g.:

The money goes directly to your PayPal Cash or PayPal Cash Plus balance where you can use it as you normally would.

How long does it take to receive money from selling crypto?

Usually, the money you receive from selling crypto will be available instantly in your PayPal Cash or PayPal Cash Plus balance. As with all transactions, crypto sales are subject to review and could be delayed or stopped if there's an issue.

if the mouse cursor is placed at the end, SHIFT + PAGE UP fails to select the entire text (only the last paragraph becomes selected). Tested on Chrome + Windows.

0
4

Bug report created on GH

Overlapping bold/italic formatting leads to incorrect formatting when toggling to Markdown mode.

  1. In rich text mode, write some text.
    • this is bold, now italic, and now?!
  2. Select part of the text.
  3. Make the selection italic.
    • this is bold, now italic, and now?!
  4. Select some overlapping text.
  5. Make the selection bold.
    • this is bold, now italic, and now?!

(Now bold and italic formatting is correctly applied to overlapping portions of the text.)

When switching to Markdown, the formatting is screwed up because Markdown doesn’t support overlapping formatting in this way: adjacent */** is ambiguous at the best of times, but Markdown wouldn’t support this even when using _ to format italics.

Here’s what the editor generates:

**this is bold, *now italic****, and now?!*

… but as mentioned, even the following isn’t really supported by Markdown as far as I’m aware (it certainly isn’t on this site):

**this is bold, _now italic**, and now?!_
4
  • 1
    The editor seems to have functioned correctly here. It split the italics. So you have a **this is bold, *now italic*** using three asterisks to close the bold and italics and then a *, and now?!* to re-enter the remainder of the italics for the part that was outside of the bold. The problem is that the parsers we have do not handle the scenario of four consecutive asterisks because of the ambiguity. I'm not sure how that's supposed to be handled. – animuson Jan 27 at 16:11
  • @animuson It could potentially be handled by using _ for italics but personally I’d be more comfortable with forbidding overlapping formatting, but that’s admittedly fairly opinionated since it (arguably) prevents “valid” markup. – Konrad Rudolph Jan 27 at 16:12
  • 1
    Ah, this is clever. In a way, you've created illegal content in the rich-text editor that isn't actually supportable in the backing markdown. The editor is "smart" enough to generate what would be sane markdown, but isn't actually valid due to the introduced ambiguity. I guess the solution here is to default weak emphasis back to _ in the case of an overlap since that is valid – Ben Kelly Jan 29 at 22:34
  • 2
    There's still some edge cases here I can think of, even using _. This is going to require a bit of thought and a few unit tests. Thanks for the report! – Ben Kelly Jan 29 at 22:43
4

Blockquoting a selection of text strips the markup of the selected text

I was working on a post, en wanted to quote a piece of a well formatted post by Shog9.

I copied and pasted this part:

### So what good is Triage?

Ok, now we can get to some numbers. From my perspective, it's *still* a better First Posts review than First Posts Review, and a better way of handling VLQ flags on questions than Low Quality review. But that doesn't *directly* help folks just trying to browse the site without bumping into lousy questions.

<!-- #24065 -->

So let's focus on views. In May of 2018, 256,414 questions were posted on Stack Overflow. Of those, 31586 entered Triage, and 25508 were reviewed completely (that is a consensus was reached). The average view count across all questions posted in May was 89; the average view count for questions that entered Triage was 64; the average view count for questions that completed Triage was 67. 

Broken down by Triage consensus:

    Triage result      Questions Avg Views 
    ------------------ --------- --------- 
    Looks Good         11379     76        
    Should Be Improved 9825      66        
    Unsalvageable      4299      48        

I then selected it, and pressed the blockquote button as I wanted to quote it.

It's markdown now looks like this:

> So what good is Triage?
> 
> Ok, now we can get to some numbers. From my perspective, it's *still* a better First Posts review than First Posts Review, and a better way of handling VLQ flags on questions than Low Quality review. But that doesn't *directly* help folks just trying to browse the site without bumping into lousy questions.
> 
> <!-- #24065 -->
> 
> So let's focus on views. In May of 2018, 256,414 questions were posted on Stack Overflow. Of those, 31586 entered Triage, and 25508 were reviewed completely (that is a consensus was reached). The average view count across all questions posted in May was 89; the average view count for questions that entered Triage was 64; the average view count for questions that completed Triage was 67. 
> 
> Broken down by Triage consensus:
> 
> Triage result      Questions Avg Views 
> 
> Looks Good         11379     76        
> Should Be Improved 9825      66        
> Unsalvageable      4299      48        

See that the heading got stripped from the first sentence, and the code indentation and dashes from the makeshift table got stripped too.

4

Peculiar behavior when trying to upload GIF

While editing this answer I ran across a strange little quirk.

When pasting GIFs into the image upload section, it is rendered as a PNG, which makes it no longer animated. When dragging files from the file explorer into the section however, it preserves file type.

Here's a GIF that illustrates the issue (above 2MB, so hosted on Imgur itself): https://imgur.com/a/F2e8T5B

2
  • It's not pasted as PNG; it's copied as a still-frame image. When you right-click a GIF and select "Copy", only one frame is copied (at least in my experience). This has nothing to do with SE. Use "Copy image address" instead. – 41686d6564 May 3 at 10:36
  • @41686d6564 Thanks for clearing things up :) – Spectric May 3 at 14:58
3

(tags don’t work yet in this mode either it would seem, although it may render properly given that this is ported to markdown)

Using a line break, breaks the user interface.

Steps to reproduce:

  1. Type some normal text

  2. Press shift+enter

  3. Press enter

As shown below:


normal text

7
  • Using an hr as shown above, when clicking edit and entering the rich text editor, creates a wrapper for the hr which is <div contenteditable=true> which is probably not ideal. – Travis J Jan 29 at 0:16
  • The example shown below is missing markup, presumably because the process of converting the rich text back to markdown is not 1 to 1. As such, my attempt to actually show the issue there doesn't do much in itself, aside from pointing out the lack of 1-1 mapping (which should be a requirement for any richtext environment). – Travis J Jan 29 at 0:17
  • Thanks for the report, but I'm having a little trouble understanding the bug, as "breaks the user interface" is a bit vague. Can you explain what behavior you're seeing and the behavior you're expecting to see? Additionally, is this in markdown or rich-text mode? – Ben Kelly Jan 29 at 21:30
  • 1
    @BenKelly - It is in rich-text mode. Once you have taken the steps, you can no longer select the element created by insertLineBreak, nor move past it. Instead, moving the cursor (or range tracker from a behind the scenes point of view) to the inserted line break causes the cursor to go to the prior element; perhaps a result of the tracker not recognizing the action and thinking it is somewhere it is not. – Travis J Jan 29 at 22:07
  • @BenKelly - You may want to whitelist the execCommand options that are available. – Travis J Jan 29 at 22:10
  • @TravisJ You may want to edit these details into your answer. – Sebastian Simon Feb 3 at 4:30
  • @SebastianSimon - This issue will be handled, it is similar in nature to several other bugs now that I have inspected most of what has been reported. It would seem that there is an issue with the tracker getting stuck. To be honest, there is a whole host of issues with creating a rich text environment, and this answer would turn into a melting pot if I started including all the sort of related nuances to this issue here. – Travis J Feb 3 at 6:33
3

When inserting a new image via CTRL + V, please don't place the "Add Image" button at the top of the editor, but instead place it somewhere closer to the cursor where the image is being inserted.

Example:

enter image description here

5
  • 1
    +1, especially as you can't hit Enter to get it. – Ollie Jan 26 at 23:47
  • 3
    The button should be focused anyway. Then, having it close to the cursor would be a "nice-to-have". – 41686d6564 Jan 27 at 4:33
  • @41686d6564 imho we shouldn't have to click or press any key – Franck Dernoncourt Jan 27 at 15:45
  • @Franck I thought of that too but then I quickly realized that this one might accidentally paste something that they don't wish to be uploaded (the same concern that animuson addressed in the comments below your answer). I'm fine with instant upload with drag-and-drop but not with Ctrl+V. – 41686d6564 Jan 27 at 20:10
  • 3
    Thanks for the suggestion! I understand the pain point, but I have to reflect a bit to figure out how I'd solve this. I'll pass this along to our designers and see if we can't come up with a good solution. – Ben Kelly Jan 29 at 22:18
3

Dim oCSV
Local $oConnection = ObjCreate()

I check how to post inline code and I have two comments:

  1. I can’t select a language .. is there always “auto” enabled and can’t be chosen manually?

  2. I had such an issue, that when I started my inline code, that the editor area was empty, so there was no new line. And when I was in “code segment“ then I was unable to go down below the area, with the “cursor down key”. I had to use Ctrl + Enter to go outside the box and then the cursor keys started working properly. My suggestion is to always automatically add a new line below the code area.

6
  • 1
    1. Asked/notified before here. 2. Continued here – Michał Lipok Jan 26 at 23:31
  • 1
    For 1, you can indicate the code language in Markdown mode, which is the same as it always has been. We haven't figured out how to allow this in rich text - you can see this noted in the question's section about how MD is best for fine-tuning posts. – Catija Jan 27 at 15:23
  • in the question's section about how MD is best for fine-tuning posts where ? – Michał Lipok Jan 28 at 20:37
  • 1
    Search the question for "Markdown mode is your go-to for fine-tuning posts" - it's a section towards the lower middle of the post. – Catija Jan 28 at 20:39
  • Now I see. Thanks. In the future: I would prefer to have an option in profile preferences to choose between 1 Auto mode 2 specific language/formating (my favorit) . But in the moment when I post code I should be able to change them by selecting from some kind of combo. btw. Auto option is/will be the best option for new users, but advanced should have a way to spcified the formationg in code segment. – Michał Lipok Jan 28 at 20:51
  • Thanks for the report! As you note, 1 is answered here (tl;dr, we're working on it). As for 2, I'm seeing a few different bugs that appear to have the same root cause. Hopefully, fixing one will fix them all – Ben Kelly Jan 29 at 22:25
3

If the image is above the max size (current 2 MiB), automatically resize (or change compression) to the largest image possible, or close to it.

2
  • 6
    While this is a reasonable request - the current editor doesn't have this functionality, so I'm not sure this is in scope. – Catija Jan 30 at 22:20
  • 5
    Is this actually feasible? The size restrictions are presumably there to reduce the load on the server, so the file resizing would need to happen client-side. Are there reliable solutions to do this in-browser? – E.P. Feb 1 at 11:11
3

On Google Chrome for Android, after clicking on the image button, one always have to scroll up to be able to click on "Browse".

Enter image description here

3

When trying to navigate from one cell to another cell by pressing tab and then trying to select all the text of the cell by shift+end keys, the selection doesn't happen the first time. I need to press shift+end twice to be able to select the cell's text.

This issue occurs on Mozilla Firefox only. On Google Chrome, it is working as expected.

Mozilla Firefox: 85.0.2 (64-bit)
Operating System: Windows 10 Pro

GIF

3

Adding an image results in removing the post.

Demo:

enter image description here

Pasted markdown:

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/ENIEY.gif

Tested on Android 10 with chrome 89.

2
3

Incorrect rendering of tables (HTML, extra row)

The following animated GIF shows the issue.

The table with no header is correctly rendered. However, on editing, when I disable markdown, it automatically adds an empty row.

Reproduce it here

More obvious comparison.

Regular preview:

enter image description here

Markdown preview:

Not only does it add an extra row, but also incorrectly renders the HTML, which causes even more problematic troubles during editing, illustrated below:

3

Bug report opened on GH

Lists are removed when quoted when markdown=on:

E.g.

- It's calc'd OTF each time there's a need to know; the status isn't stored in a variable on the Profile. Sources: [meta.stackexchange.com/questions/309220/…](https://meta.stackexchange.com/questions/309220/warn-new-users-who-ran-into-a-question-ban-on-other-sites-before-they-post-here?rq=1#comment1007747_309220 "warn new users who ran into a question ban on other sites before they post here") [meta.stackexchange.com/questions/309220/…](https://meta.stackexchange.com/questions/309220/warn-new-users-who-ran-into-a-question-ban-on-other-sites-before-they-post-here?rq=1#comment1007752_309220 "warn new users who ran into a question ban on other sites before they post here") [meta.stackexchange.com/questions/309220/…](https://meta.stackexchange.com/questions/309220/warn-new-users-who-ran-into-a-question-ban-on-other-sites-before-they-post-here?rq=1#comment1008668_309220 "warn new users who ran into a question ban on other sites before they post here") - Can chng b4 posting – [Rob](https://meta.stackexchange.com/users/282094/rob "13,587 reputation") [15 hours ago](https://meta.stackexchange.com/questions/363950/if-a-user-is-banned-from-posting-answers-state-so-before-they-start-writing-the#comment1214462_363950)
- To expand off Rob's comment: because they are calculated on the fly, it is also an expensive thing to check. Running that check every single time a user loads a question page is not viable at all. Only running it when someone attempts to post an answer reduces resource load. – [animuson](https://meta.stackexchange.com/users/141525/animuson "172,484 reputation")**[♦](https://meta.stackexchange.com/users/141525/animuson "172,484 reputation")** [15 hours ago](https://meta.stackexchange.com/questions/363950/if-a-user-is-banned-from-posting-answers-state-so-before-they-start-writing-the#comment1214464_363950)
- Similar cross-site duplicates, which offer insights into the mechanism: [meta.stackoverflow.com/q/318202/3648282](https://meta.stackoverflow.com/q/318202/3648282) [meta.stackoverflow.com/a/323194/3648282](https://meta.stackoverflow.com/a/323194/3648282) - you can have a warning or message, but until you actually push the button you don't know the *true* answer. The permission to post can change a moment later, any message prior to actually pushing the button would be an estimate of what you should expect the result to be; and not the actual result. – [Rob](https://meta.stackexchange.com/users/282094/rob "13,587 reputation") [4 hours ago](https://meta.stackexchange.com/questions/363950/if-a-user-is-banned-from-posting-answers-state-so-before-they-start-writing-the#comment1214520_363950)

becomes:

> It's calc'd OTF each time there's a need to know; the status isn't stored in a variable on the Profile. Sources: [meta.stackexchange.com/questions/309220/…](https://meta.stackexchange.com/questions/309220/warn-new-users-who-ran-into-a-question-ban-on-other-sites-before-they-post-here?rq=1#comment1007747_309220 "warn new users who ran into a question ban on other sites before they post here") [meta.stackexchange.com/questions/309220/…](https://meta.stackexchange.com/questions/309220/warn-new-users-who-ran-into-a-question-ban-on-other-sites-before-they-post-here?rq=1#comment1007752_309220 "warn new users who ran into a question ban on other sites before they post here") [meta.stackexchange.com/questions/309220/…](https://meta.stackexchange.com/questions/309220/warn-new-users-who-ran-into-a-question-ban-on-other-sites-before-they-post-here?rq=1#comment1008668_309220 "warn new users who ran into a question ban on other sites before they post here") - Can chng b4 posting – [Rob](https://meta.stackexchange.com/users/282094/rob "13,587 reputation") [15 hours ago](https://meta.stackexchange.com/questions/363950/if-a-user-is-banned-from-posting-answers-state-so-before-they-start-writing-the#comment1214462_363950)
> To expand off Rob's comment: because they are calculated on the fly, it is also an expensive thing to check. Running that check every single time a user loads a question page is not viable at all. Only running it when someone attempts to post an answer reduces resource load. – [animuson](https://meta.stackexchange.com/users/141525/animuson "172,484 reputation")**[♦](https://meta.stackexchange.com/users/141525/animuson "172,484 reputation")** [15 hours ago](https://meta.stackexchange.com/questions/363950/if-a-user-is-banned-from-posting-answers-state-so-before-they-start-writing-the#comment1214464_363950)
> Similar cross-site duplicates, which offer insights into the mechanism: [meta.stackoverflow.com/q/318202/3648282](https://meta.stackoverflow.com/q/318202/3648282) [meta.stackoverflow.com/a/323194/3648282](https://meta.stackoverflow.com/a/323194/3648282) - you can have a warning or message, but until you actually push the button you don't know the *true* answer. The permission to post can change a moment later, any message prior to actually pushing the button would be an estimate of what you should expect the result to be; and not the actual result. – [Rob](https://meta.stackexchange.com/users/282094/rob "13,587 reputation") [4 hours ago](https://meta.stackexchange.com/questions/363950/if-a-user-is-banned-from-posting-answers-state-so-before-they-start-writing-the#comment1214520_363950)

enter image description here

5
2

Add progress bar when uploading an image.

enter image description here

1

I can't use the ESC key to exit this new editor.

I like keyboard shortcuts, and this worked just fine for the old editor, for both questions and answers. Can we implement the shortcut for this editor?

1 2 3
4

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .