Bug 60774 - HTML Assertion element does not handle HTML5 valid code
Summary: HTML Assertion element does not handle HTML5 valid code
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 2.13
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-25 22:01 UTC by Philippe Mouawad
Modified: 2017-12-08 14:48 UTC (History)
2 users (show)


Attachments
Test plan showing issue (7.29 KB, application/xml)
2017-02-25 22:01 UTC, Philippe Mouawad 		Details
Enable a second parser (Jsoup) to check for html correctness (7.54 KB, patch)
2017-02-26 12:18 UTC, Felix Schumacher 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2017-02-25 22:01:08 UTC 
The element uses an old jtidy library which does not handle HTML5.
See attached Test plan which is ok validated against:
https://html5.validator.nu/
Comment 1 Philippe Mouawad 2017-02-25 22:01:48 UTC 
Created attachment 34779 [details]
Test plan showing issue
Comment 2 Felix Schumacher 2017-02-26 12:18:23 UTC 
Created attachment 34780 [details]
Enable a second parser (Jsoup) to check for html correctness
Comment 3 Philippe Mouawad 2017-02-26 12:25:15 UTC 
(In reply to Felix Schumacher from comment #2)
> Created attachment 34780 [details]
> Enable a second parser (Jsoup) to check for html correctness

Great , I missed this feature Felix.

I would suggest dropping JTidy or at least make JSoup the default.
Regards
Comment 4 Philippe Mouawad 2017-02-26 12:45:40 UTC 
Hi,
JSoup seems to consider html5 only. 
So "omit", "auto", "strict", "loose" would not be used by it.
I am not sure they even reflect current state of HTML (xhtml transitional, html5, xhtml strict (!= strict which would be for html4 ?) )
 
How can we make us of them with jsoup ?
Comment 5 The ASF infrastructure team 2022-09-24 20:38:07 UTC 
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4298