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

Why, in a HTML 4.01 Transitional document, does JHOVE 'forget' an open span tag when there is a p inside? #928

Open
RvanVeenendaal opened this issue Jul 3, 2024 · 0 comments
Assignees
Labels
bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release
Milestone

Comments

@RvanVeenendaal
Copy link

In the attached file (save as .html), JHOVE 1.30 reports a close (span) tag without open (span) tag at line 173. In Dutch: "ErrorMessage: Sluit tag zonder een overeenkomende open tag: Name = span, Line = 173, Column = 8". Inside this span there are two p(aragraph)s. This seems to be illegal: a span tag is an inline element which can not contain block elements like p. This is why JHOVE also reports (in Dutch): "ErrorMessage: Tag illegaal in deze context: Name = p, Container = span, Line = 171, Column = 8".

Why does JHOVE seem to have 'forgotten' about the open span tag at line 170 when it encounters the p tags inside the span? Bug or feature?

i000000.xml.html.txt This file is part of a 2002 website that can be accessed here: https://www.nationaalarchief.nl/onderzoeken/archief/2.04.115/invnr/4ED/file?eadID=2.04.115&unitID=4ED&query=staatssecretaris%20de%20vries.

@carlwilson carlwilson self-assigned this Aug 22, 2024
@carlwilson carlwilson added the bug A product defect that needs fixing label Aug 22, 2024
@carlwilson carlwilson added this to the JHOVE 1.34 milestone Aug 22, 2024
@carlwilson carlwilson added the P1 High priority issues to be scheduled in the upcoming release label Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release
Projects
None yet
Development

No branches or pull requests

2 participants