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.

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

[BUG] ol element not showing numbers #435

Closed
michael-letcher opened this issue Jan 18, 2018 · 1 comment
Closed

[BUG] ol element not showing numbers #435

michael-letcher opened this issue Jan 18, 2018 · 1 comment

Comments

@michael-letcher
Copy link
Contributor

Overview of the issue

Using this mark up I'd expect to see a numbered list

1. Make sure you have the latest code on the parent and submodules before you make any commit (fetch + pull).
1. Commit your submodule changes first (if any) before the parent changes. If you try to commit your parent changes first, SourceTree will throw an error.
    * Make sure that your HEAD is not detached from master => when committing make sure you are committing to master.
1. Then commit your changes in the parent repository (if any).
1. If a new commit has been made in the submodule, a new change will appear in your parent repository.
    * This is the submodule commit that the parent is pointing at. Commit this too. If it's not there, preform a fetch.
Operating System, Node.js, npm, compodoc version(s)
OSX 10.13.1
Node 6.11.2
Compo 1.0.5
Angular configuration, a package.json file in the root folder

NA

Compodoc installed globally or locally ?

Locally

Motivation for or Use Case

Basic Markdown that should be displayed correctly

Reproduce the error

Create an ordered list

Related issues
Suggest a Fix
.content ol {
    list-style-type: decimal;
    margin-top: 0;
    padding-left: 20px;
    margin-bottom: 16px;
}
@lock
Copy link

lock bot commented Sep 30, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants