Comments (10)
Could you use permalink from demo to show exacty input and output, and put correct output to gist ?
from markdown-it.
Also, please, reduce example to minimal possible.
from markdown-it.
Ok, I will do it later.
from markdown-it.
from markdown-it.
See http://spec.commonmark.org/0.15/#html-blocks
We follow commonmark spec, and result is exactly as required by spec.
from markdown-it.
I see 2 possible solutions:
- Write your own rule to replace existing html_block
- Just fix your markup to be CommonMark-compatible (avoid empty lines in html blocks)
I understand, that result can be not as you expect, but this it NOT a bug.
from markdown-it.
Understood.
Github do too much in Makedown's compatibility, that is sad.
from markdown-it.
Closing? Or need advices how to rewrite html_block rule ?
from markdown-it.
That would be another issue.
from markdown-it.
FYI http://talk.commonmark.org/t/raw-html-blocks-proposals-comments-wanted/983?u=vitaly HTML blocks are now discussed. Not sure about this case, but general improvments are expected soon.
from markdown-it.
Related Issues (20)
- Using whitespace as a closing delimiter HOT 9
- A proper plugin documentation for Markdown-it HOT 3
- Reconstruct Markdown document from the tokens? HOT 6
- Linkify breaks simple italics syntax HOT 1
- Replace Node's deprecated punycode HOT 3
- Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'references') HOT 1
- Run ./benchmark/benchmark.js does not work HOT 1
- Error running benchmark HOT 3
- Support GFM Notes HOT 2
- Pause animated gifs HOT 2
- value of alt attribute in image token is empty HOT 2
- Vue Error with new version Can't import the named export 'P' from non EcmaScript module (only default export is available) HOT 4
- Add Alerts HOT 1
- Allow tree-shaking of unused rules and dependencies HOT 1
- Unsupported engine WARN EBADENGINE current: { node: 'v16.20.1', npm: '8.19.4' } HOT 2
- Data URI images are filtered even when validateLinks is disabled HOT 1
- Have you ever encountered the problem of going from <p> to <h1> during parsing? HOT 1
- Has anyone encountered the situation where the <p> suddenly changed to an <h1> and then to a <p> during parsing?
- Has anyone encountered the situation where the <p> suddenly changed to an <h1> and then to a <p> during parsing? HOT 1
- Access the Token class when loading the library from a script tag
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from markdown-it.