Bugzilla

I can only guess, but I think there's a space missing between "here" and "<http". The text recongnizer recognizes "here http://foo there" and "here <http://foo> there", but cannot recognize "here<http://foo>". No human writes "here<http". Remember that the recognizer does *heuristics* for normal plaintext.

Given that some stupid software seems to output this malformed plaintext: The quick and dirty fix is to simply replace all "<http" with " <http", before recognizing. That should be a 1-line fix, in the right place, where the ICS plaintext is parsed, before sending it to scanHTML().

The real fix is not to use that plaintext, but to use the original HTML. As it happens, we (Beonex, my company) is working on that right now, to make Lightning properly support HTML descriptions from start to finish. We plan to be contributing that to TB/Lightning trunk, in another bug.

Thanks, Thomas D, for ccing me on this. I'm happy to help here.

I can only guess, but I think there's a space missing between "here" and "<http". The text recongnizer recognizes `here http://foo there` and `here <http://foo> there`, but cannot recognize `here<http://foo>`. No human writes `here<http`. Remember that the recognizer does *heuristics* for normal plaintext.

Given that some stupid software seems to output this malformed plaintext: The quick and dirty fix is to simply replace all "<http" with " <http", before recognizing. That should be a 1-line fix, in the right place, where the ICS plaintext is parsed, before sending it to scanHTML().

The real fix is not to use that plaintext, but to use the original HTML. As it happens, we (Beonex, my company) is working on that right now, to make Lightning properly support HTML descriptions from start to finish. We plan to be contributing that to TB/Lightning trunk, in another bug.

Thanks, Thomas D, for ccing me on this. I'm happy to help here.

I can only guess, but I think there's a space missing between "here" and "<http". The text recongnizer recognizes `here http://foo there` and `here <http://foo> there`, but cannot recognize `here<http://foo>`. No human writes `here<http`. Remember that the recognizer does *heuristics* for normal plaintext.

Given that some stupid software seems to output this malformed plaintext: The quick and dirty fix is to simply replace all "<http" with " <http", before recognizing. That should be a 1-line fix, in the right place, where the ICS plaintext is parsed, before sending it to scanHTML().

The real fix is not to use that plaintext, but to use the original HTML. As it happens, we (Beonex, my company) are working on that right now, to make Lightning properly support HTML descriptions from start to finish. We plan to be contributing that to TB/Lightning trunk, in another bug.

Thanks, Thomas D, for ccing me on this. I'm happy to help here.

I can only guess, but I think there's a space missing between "here" and "<http". The text recongnizer recognizes `here http://foo there` and `here <http://foo> there`, but cannot recognize `here<http://foo>`. No human writes `here<http`. Remember that the recognizer does *heuristics* for normal plaintext.

Given that some stupid software seems to output this malformed plaintext: The quick and dirty fix is to simply replace all "<http" with " <http", before recognizing. That should be a 1-line fix, in the right place, where the ICS plaintext is parsed, before sending it to scanHTML().

The real fix is not to use that plaintext, but to use the original HTML. As it happens, we (Beonex, my company) are working on that right now, to make Lightning properly support HTML descriptions from start to finish. We plan to be contributing that to TB/Lightning trunk, in bug 1607834.

Thanks, Thomas D, for ccing me on this. I'm happy to help here.