[
https://issues.apache.org/jira/browse/TIKA-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048544#comment-15048544
]
Markus Jelsma commented on TIKA-1808:
-------------------------------------
Hello Ken - that makes sense indeed, if it is not valid, close the head and
ignore the rest. And if this is a feature, not a bug, we need HTMLSchema to
support the wide range of crap sites on the web.
I would also be interested to see that JSoup does.
> Head section closed too eager
> -----------------------------
>
> Key: TIKA-1808
> URL: https://issues.apache.org/jira/browse/TIKA-1808
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.11
> Reporter: Markus Jelsma
> Fix For: 1.12
>
>
> XHTMLContentHandler has some logic that closes the head section too early, or
> this is a problem in TagSoup. In this [1] case a <div> element appears in the
> head, causing the head to be closed. Subsequent <head> elements do not appear
> in custom ContentHandlers so i cannot read the document's title, or any other
> meta tags.
> It can be fixed by using a custom HTMLSchema in the ParseContext, e.g.
> schema.elementType("div", HTMLSchema.M_EMPTY, 65535, 0); but this isn't
> really an elegant solution.
> [1] http://www.aljazeera.com/news/2015/05/150516182251747.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)