95

For these posts, we’ve built a tool that automatically fixes these well-known issues by changing a post’s Markdown source directly and re-rendering the HTML of the post in question. When we change a post’s Markdown automatically, this will end up looking like a regular edit but we’re making sure that this won’t bump posts to the top. What will this do for ...


70

Migration Schedule Here's an overview of the sites we're going to migrate, when we're planning to run the migration and the current status of that site. I'll keep it updated as we go. We might run into some issues along the way, so please understand that predicting an exact timeline is hard and we're going to adapt as we go. Current Status First migrations ...


39

If you deprecate the use of <!-- language: lang-html --> in favor specifying the prettifier at the start of the code-fence, will you still support the overall syntax highlight hint for all code blocks? <!-- language-all: lang-none --> I have used that feature very occasionally so I doubt it has much impact if it can't be used anymore. For ...


29

How will old revisions, in cases where they would trigger edits if they were current, be displayed when viewed? To clarify my motivation for this question: As I understand it, each post that is currently not valid CommonMark will be updated by one non-bumping edit (which I presume will be shown as having been performed by the Community bot), translating the ...


27

Things might get funky when you're editing a post that renders differently with the new CommonMark renderer. If someone starts editing one of these posts that cannot be automatically updated, will there be some kind of notification that the editor should pay extra attention to the render preview because the edit may alter the appearance of the post? This ...


26

Is this going to apply to chat as well? That has its own quirks in its implementation that are different from the main site (such as having to do > quote for a quote when >quote works on the main site). Is that going to change in any way?


20

Do you have a list of all the 'well-known issues' that will be automatically converted? For example, I make heavy use of the <!-- language: python --> syntax. Will that be converted to code fences? Will we be notified if one of our own post can't be converted, so that we can edit them ourselves? Or will it go to a dedicated queue? Should we try to ...


16

Block Quote migration bug status-reproduced I received strange "Commonmark migration" edits here: https://meta.stackexchange.com/posts/344867/revisions https://meta.stackexchange.com/posts/345953/revisions Both quote whitespace formats appear to be valid CommonMark syntax, so I don't know why they were migrated in the first place. The post-...


16

Do you also change the syntax highlighter at this occasion? If I remember correctly, SE still uses Google Prettify, which has been discontinued. Support for more languages and new language versions would be great!


16

I seem to remember that CommonMark includes additional syntax beyond what SE supported so far, specifically bracketed enumeration, i.e. 1), in addition to dotted numbers for creating enumeration lists. Is this true and would this mean bracketed numbers will now be automatically turned into enumeration lists (ordered lists, or <ol>)? This would be an ...


13

June 2020 Targets: Respond to 50% of Meta posts from across the network, within 2 weeks of status-review getting added to it. Set targets for responding to "leftovers" from previous periods. Set targets and guidance for older posts (particularly posts not relating to current projects). Guidance: Community-specific concerns: anything, from policies to ...


13

Mathjax Things like spoilers, MathJax, circuit diagrams, stack snippets, etc. are used on several network sites. We're going to continue to support all of those custom syntax elements even if they're not part of the official CommonMark specification. Just to be clear, Physics SE and Mathematics SE would be severely crippled if MathJax support was damaged....


12

bug help-center status-completed A small detail maybe, but the formatting help pages may also need to be adapted. Example from the Meta Stack Exchange formatting help page: > The > on the blank lines is optional. > Include it or don't; Markdown doesn't care. > > But your ... Whereas the original post says: Blockquotes Previously, empty ...


11

What was broken that needed fixing? I apologize if I come off as ungracious, as you spent a lot of time working on this, but what was it that required fixing? Seriously. I've had very few problems using this interface. What pressing need does this serve? This question is based on a lot of years of experience of being immersed in "change for the sake ...


10

What about mobile support? I understand that the existing apps are no longer maintained, but it seems that plenty of people are still using them, whether or not that is a good idea. My assumption: when the client side renderer changes, that will render all existing (no longer supported) mobile apps will be really broken and unusable after this change? (...


9

For these posts, we’ve built a tool that automatically fixes these well-known issues by changing a post’s Markdown source directly and re-rendering the HTML of the post in question. When we change a post’s Markdown automatically, this will end up looking like a regular edit but we’re making sure that this won’t bump posts to the top. For users who are ...


8

bug help-center status-completed You can still use indented code blocks but can’t declare the preferred language explicitly moving forward. The Help Center is still mentioning this old method: To manually specify the language of an indented code block, insert an HTML comment like this before the block: <!-- language: lang-js --> setTimeout(...


7

Couple of questions: Are you going to update the HTML (since it is cached) or just the raw Markdown code? Are you also going to add an entry in the edit history, presumably saying that Community made the change?


7

Did I understand correctly that you will be fixing the compatibility issues listed automatically, like more indentation necessary for list paragraphs, quote markup before empty lines, missing spaces before headlines,...? It might very well be that the question covered that already under the general migration explanations, but I just want to make super sure ...


3

Multi-paragraph quote blocks within lists bug The automatic migration on Movies & TV omitted this answer, either because it failed to convert it into an HTML that didn't change or because it didn't recognize it as a case that needs adaptation. However, it clearly needs it since it has both multi-paragraph quote blocks and multi-paragraph bullet points ...


3

bug status-bydesign When we change a post’s Markdown automatically, this will end up looking like a regular edit but we’re making sure that this won’t bump posts to the top. I've noticed several posts here on Meta that seem to have been bumped by the community user's "Commonmark migration" edit to an answer: The 3rd revision to this answer for ...


3

Why not leave the rendered HTML for old posts alone, as was done for previous updates to the Markdown renderer (iirc)?


Only top voted, non community-wiki answers of a minimum length are eligible