Fragments are occasionally skipped

[toiletbril]

Hello! Thanks for the awesome library. I use it in my project, dedoc.

Some time ago, I encountered a problem that occasionally, even though they are present in the HTML, the fragments are skipped and nowhere to be found in TaggedLine's elements.

I took time to investigate, and it seems that this bug occurs when FragmentStart is the only element in the tagged line.

Since the TaggedLineElement is considered as having no content if it's a FragmentStart:

rust-html2text/src/render/text_renderer.rs

Lines 128 to 137 in 240a4cc

	impl<T> TaggedLineElement<T> {
	/// Return true if this element is non-empty.
	/// FragmentStart is considered empty.
	fn has_content(&self) -> bool {
	match self {
	TaggedLineElement::Str(_) => true,
	TaggedLineElement::FragmentStart(_) => false,
	}
	}
	}

The TaggedLine is considered empty when it's made exclusively of FragmentStart elements:

rust-html2text/src/render/text_renderer.rs

Lines 186 to 193 in 240a4cc

	fn is_empty(&self) -> bool {
	for elt in &self.v {
	if elt.has_content() {
	return false;
	}
	}
	true
	}

TaggedLine, which contain only FragmentStart elements are lost. Seems like due to this condition:

rust-html2text/src/render/text_renderer.rs

Line 365 in 240a4cc

if !self.word.is_empty() {

Attached is an page with fragments, taken from golang documentation, which is affected by the issue.
example_page.txt

Is this the desired behavior?

[jugglerchris]

Thanks for the report and detailed investigation!

That does seem wrong - I think even if suppressing blank lines, any fragments ought to be carried over to the next one.