MD033 allowed_elements highlights the wrong element in mixed element scenarios
See original GitHub issueIn VS Code, the markdownlint allowed_elements setting works for other html elements that I have tried, but not <details>
. For example, with the following there are no warnings for h1 or p (as expected), but details still gets a warning :
"markdownlint.config": {
"MD013": false,
"no-inline-html": {
"allowed_elements": [ "details", "h1", "p" ]
}
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Allow some HTML elements in markdown lint rule MD033 in ...
When authoring Markdown in Visual Studio Code with the markdownlint extension installed, I am seeing lint message MD033/no-inline-html: ...
Read more >Untitled
Examples sea sponges, Jorge doimeadios, Drama lakonan rosley idris, Weapon app pc, ... Greek punk mix, Common kingdom remix mp3, Mishima technique pottery, ......
Read more >FEDERAL REGISTER - GovInfo
The FEDERAL REGISTER (ISSN 0097–6326) is published daily,. Monday through Friday, except official holidays, by the Office.
Read more >Inline elements - HTML: HyperText Markup Language | MDN
In this article, we'll examine HTML inline-level elements and how they ... following paragraph is a <p class="highlight">block-level element ...
Read more >Log | Future of Coding
For all it's faults, the internet has allowed us all to find each other ... I don't mind that the GUI elements are...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Creating an empty directory with the following Markdown file in it, opening the folder in VS Code with the
markdownlint
extension, and viewing the file reportsMD033
violations for both instances ofp
anddetails
as expected:179.md
Adding the following configuration file to that directory suppresses those violations as expected:
.markdownlint.json
Could you please provide an example file/scenario where this does not work for you?
The problem seems to be with with an embedded
tag. If you paste the following line into your code it will incorrectly warn about the:
Short version
Longer version with more detail