Invalid HTML and syn feeds
Short, concise description of the idea
For syndicated entries, don't break the link to the original entry if the entry contains invalid HTML.
Full description of the idea
When a journal post is made with certain invalid HTML, LiveJournal's HTML cleaner catches it. It disables all HTML in the entry, and prints an error message at the top of the entry like "[Error: Irreparable invalid markup ('<a [...] badly-closed-tag>') in entry. Owner must fix manually. Raw contents below.]"
When content from another site is syndicated onto LiveJournal, LiveJournal adds a link to the original "entry" (or whatever the other site calls the unit being syndicated) at the top of the LiveJournal post.
When a syndicated feed has bad HTML, this HTML-disabling happens like it would with any other entry. There are at least two problems with this. First, the automatically-added link to the original entry is disabled, just like with any HTML that was in the original entry itself. Second, the error message is inaccurate, since there's no "owner" of the syndicated feed, and in fact the owner of the original site might not even know there's a problem, if their site has less strict HTML cleaning and if they never read their LiveJournal syndicated feed. This error message should be changed to more accurately reflect what's going on here (though I don't have any specific text in mind; haven't thought about it yet).
- A useful link (to the original entry) is retained in more situations
- Clearer error messages are always a good thing
An ordered list of problems/issues involved
- Implementing a special case for the HTML cleaner (to not fail the entire entry, just the original not-added-by-LiveJournal stuff, and only on syn feeds) might be difficult, though I'm not sure
- Similarly, a special case for that error message might be tough to add
- There might be sentiment that the entire entry should be broken, to encourage better HTML, though I disagree with this
An organized list, or a few short paragraphs detailing suggestions for implementation
- The HTML cleaner and text of the error message need to be edited and special-cased, as explained above