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

ebml_schema2html.xsl "max" column wrong if no maxOccurs attribute #379

Closed
mbunkus opened this issue May 22, 2020 · 0 comments
Closed

ebml_schema2html.xsl "max" column wrong if no maxOccurs attribute #379

mbunkus opened this issue May 22, 2020 · 0 comments
Labels
bug website for matroska.org

Comments

@mbunkus
Copy link
Contributor

mbunkus commented May 22, 2020

For example, the BlockAdditionMapping element is defined as having neither a minOccurs nor a maxOccurs attribute, However, the "max" column created contains the value 1, which is obviously wrong for such elements.
@mbunkus mbunkus added the bug label May 22, 2020
@robUx4 robUx4 added the website for matroska.org label May 22, 2020
@robUx4 robUx4 mentioned this issue May 22, 2020
Merged
@mbunkus mbunkus closed this as completed May 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug website for matroska.org
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mbunkus @robUx4