MacDownApp / MacDownApp/macdown

HTML tags in MD not rendered properly

Open
#517 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rich Text Format
Stars
9.8k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

Hey. In MacDown 0.5.2 I encountered some strange behaviours when I use HTML tags in my MarkDown.

If I use the following MarkDown:

```
The ** block contains a navigation bar (using the HTML5 ** tag) and a table. The interesting part of this *table* definition is the provided *data-url* attribute. It is interpreted by Bootstrap Table to load the data. Our definition points to our previously created REST endpoint.
Which part of our JSON objects is used in which column is defined via the *data-field* attribute. Can you spot the match on the attribute name?
```

I get the following preview:
![screen shot 2015-12-13 at 17 57 57](https://cloud.githubusercontent.com/assets/281551/11768379/2808e73c-a1c3-11e5-95ee-1d7e2393af70.png)

Not sure if this is the wanted behaviour.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the supplied Markdown in MacDown 0.5.2 and compare the preview with the reported screenshot, then trace the Markdown/HTML preview entry point. The expected rendering must be established before work begins; done means the example renders as intended and the behavior is covered by a regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, markdown
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.