Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Known failures page? #1750

Closed
RunDevelopment opened this issue Feb 18, 2019 · 2 comments · Fixed by #1876
Closed

Known failures page? #1750

RunDevelopment opened this issue Feb 18, 2019 · 2 comments · Fixed by #1876
Labels
docs website

Comments

@RunDevelopment
Copy link
Member

Right now, known failures are documented on the examples page of the language. (So languages also have comments in their definitions. E.g. Less)

Wouldn't it be good to have one page where all known failures are documented?

Thoughts?
@ExE-Boss
Copy link
Contributor

I agree with this, because when I wanted to see all known failures, I had to load all language examples and use ctrl+F.

@Golmote
Copy link
Contributor

Golmote commented Apr 22, 2019

Agreed. Do remember, though, that currently each language has its own simple HTML page for examples and failures. We lack a standard way of providing those.

@RunDevelopment RunDevelopment mentioned this issue Apr 27, 2019
Merged
mAAdhaTTah pushed a commit that referenced this issue Jun 30, 2019
@RunDevelopment @mAAdhaTTah
Known failure page (#1876)
36a5fa0 
This PR adds a known failures page. This resolves #1750.

The known failures are moved from the example pages.
(I also updated all example pages with invalid HTML.)

Some known failures were actually fixed in the meantime but never updated, so I removed a few. Those were: 
- Handlebars
- Markdown's nested bold-italic
- Smarty
- Textile's "Nested styles are only partially supported"

### Screenshot

<details>

![image](https://user-images.githubusercontent.com/20878432/56849438-7eca3200-68f4-11e9-9dc3-bf0256be8d1e.png)

</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs website
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Known failure page RunDevelopment/prism
3 participants
@Golmote @ExE-Boss @RunDevelopment