Inconsistent Markdown rendering of equation blocks in enumerated lists

[blsz]

How to consistently render a math block inside a list item without restarting the list numbering?

The second equation is not rendered. Why? The first two equations are both indented with 4 spaces, The third is indented with 2 spaces.

1. First equation, indented with 4 spaces

   $$ a=b $$

2. Second equation, indented with 4 spaces

   $$
   c=d
   $$

3. Third equation, indented with 2 spaces

$$ e=f $$

Markdown source:

1. First equation, indented with 4 spaces

    $$
    a=b
    $$

1. Second equation, indented with 4 spaces

    $$
    c=d
    $$

1. Third equation, indented with 2 spaces

  $$
  e=f
  $$

I suspect the first block equation is incorrectly rendered as math when it should have been rendered as source code because it was indented with 4 spaces, which seems to be a bug and a minor inconsistency.

The bigger problem is that indenting with 2 spaces interrupts the list numbering in GitHub editor Preview and in GitHub Pages.

1. First equation, indented with 2 spaces

$$ a=b $$

1. Second equation, indented with 2 spaces

$$ c=d $$

1. Third equation, indented with 2 spaces

$$ e=f $$

Markdown source:

1. First equation, indented with 2 spaces

  $$
  a=b
  $$

1. Second equation, indented with 2 spaces

  $$
  c=d
  $$

1. Third equation, indented with 2 spaces

  $$
  e=f
  $$

More inconsistencies appear when the block mode math is written in single lines and when using equation environments. The numbering is continued except in the last 2 cases!

1. First equation, indented with 4 spaces, single line

   $$a=b$$

2. Second equation, indented with 4 spaces, single line

   $$c=d$$

3. Third equation, indented with 2 spaces, single line

$$e=f$$

1. Fourth equation, indented with 2 spaces, multiple line equation forced into a single line, list enumeration is interrupted

$$\begin{equation*}\begin{split}g=h\\i=j\end{split}\end{equation*}$$

1. Fifth equation, indented with 2 spaces, multiple line equation, list enumeration is interrupted

$$ \begin{equation*} \begin{split} g=h \\\ i=j \end{split} \end{equation*} $$

Markdown source:

1. First equation, indented with 4 spaces, single line

    $$a=b$$

1. Second equation, indented with 4 spaces, single line

    $$c=d$$

1. Third equation, indented with 2 spaces, single line

  $$e=f$$

1. Fourth equation, indented with 2 spaces, multi-line equation forced into a single line, list enumeration is interrupted

  $$\begin{equation*}\begin{split}g=h\\\\i=j\end{split}\end{equation*}$$

1. Fifth equation, indented with 2 spaces, multi-line equation, list enumeration is interrupted

  $$
  \begin{equation*}
  \begin{split}
  g=h \\\\
  i=j
  \end{split}
  \end{equation*}
  $$

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[blsz]

If the solution is to use ```math syntax then the solution is incompatible with all other markdown environments and not a good solution.