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

Principles and Guidelines say "undefined" #514

Closed
mitchellevan opened this issue Sep 12, 2024 · 2 comments · Fixed by #517
Closed

Principles and Guidelines say "undefined" #514

mitchellevan opened this issue Sep 12, 2024 · 2 comments · Fixed by #517
Assignees

Comments

@mitchellevan
Copy link
Contributor

Current behavior

This issue is occurring today in the editor's draft.

For the Principles and the Guidelines, the word "undefined" is appearing between the name and the description.

Example:

1. Perceivable

undefined

Information and user interface components must be presentable to users in ways they can perceive.

Screenshot of the example:

Screenshot of the example

The Criteria do not have this issue, because text such as "(Level A)" is appearing as expected in the Criteria.

Expected behavior

For the Principles and Guidelines, there should be no text between the name and the description.

For the Criteria, text such as "(Level A)" should appear as it currently does.

@mitchellevan
Copy link
Contributor Author

Hi @daniel-montalvo, please note this new issue. I'm guessing it's related to #507.

@maryjom
Copy link
Contributor

maryjom commented Sep 13, 2024

@daniel-montalvo looks like some additional script or checking in the script would be needed to only be looking for and inserting a level if it is an SC, and not for principles and guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants