-
Notifications
You must be signed in to change notification settings - Fork 1
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
HTML Attributes Ignored on Images #90
Comments
The underlying bug is that HTML attributes ( The bug is now fixed in the Thanks for reporting this bug. |
Fuzz Testing?Since the PML syntax is quite complex in terms of all the possible combinations of nodes and attributes, types of attributes values, as well node contexts, it's going to be very hard to be able to manually cover all possible test conditions (both valid and invalid, to test successes and proper error handling). Probably the best solution would be to rely on fuzz testing instead. I believe there are various Java libraries for fuzz testing, either native or ported (e.g. JQF). Although it would require investing energy on its initial setup, I believe it's worth the costs since it will therefrom grant solid test coverage for all the various combinations between nodes, and between nodes and their attributes. If I've understood correctly, most fuzzing libraries require you define a rule-based driver, via some sort of grammar describing a template for the possible combinations in the generated input sources fed to to test unit. With syntaxes like PML, it's just too hard to manually cover all edge cases testing, and bugs tend to get by unnoticed for a long time. |
Interesting idea! |
Fixed in version 4.0.0 |
I noticed that with PMLC 3.1.0 I'm failing to render HTML Attributes for images
alt
ortitle
text:both statements will just produce the following HTML snippet:
As far as I can remember, both used to work fine in my previous tests with PML 2.x, and the
html_alt
is even mentioned in the PML User Manual examples.I haven't had a chance to test whether this is affecting just images or other elements too, but it definitely looks like a bug that crept in with the latest updates (either 3.0 or 3.1.0).
The text was updated successfully, but these errors were encountered: