Issue with MarkDown filter and HTML...

[jim]

I noticed that the MarkDown fiter doesn't always parse out HTML blocks correctly. For example, in this test each tag is sent as content individually - rather than as a full block.

Instead of "<ul><li>item1</li><li>item2</li></ul>"

Several calls are made to the subfilter (html) like this:

"<ul>"
"<li>"
"item1"
etc..

This makes it impossible for state information to be processed correctly. The tests were probably working before because of a bug in the HTML filter (now fixed).

@Test
public void testUlInTable() throws Exception { // Okapi issue #685
    testRoundTrip("ul-in-table.md");
}

[Chase Tingley]

There’s an issue on this already: 

https://bitbucket.org/okapiframework/okapi/issues/928/the-markdown-filter-does-not-handle-html

See the discussion about halfway down (Mihai, Kuro, and I) about complexity.

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/659b8fdf-f344-8515-d4e6-0496f22548af%40gmail.com.

[jim]

Ah, I see. This is also related to Kuro's comments in the "Step for inline codes" thread.

For now I will try to work around the exception by tweaking the HTML rule configuration logic. I think this particular case  with "<ul>" is a bug in the AbstractMarkupFilter. "<ul>" is being flagged as an EXCLUDED_ELEMENT tag adn expects to be balanced - but this is incorrect.

thanks,

Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-devel/CAGRYq4jh697i0HxC95jeQfWmNU_Teg8it0uF2bXuvKY1Sv68bQ%40mail.gmail.com.