View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010772 | mantisbt | rss | public | 2009-07-27 14:02 | 2021-01-17 04:38 |
Reporter | mantisams | Assigned To | |||
Priority | high | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Google Chrome | OS | Windows XP | ||
Product Version | 1.1.8 | ||||
Summary | 0010772: RSS feed does not appear proper formatted in Google Chrome | ||||
Description | Check RSS feed in Google Chrome.....you will find that it will not appear properly formatted as that of other browsers. | ||||
Steps To Reproduce |
| ||||
Tags | admin | ||||
the same happen in google reader |
|
If this is the same issue I had with Google Reader, all paragraphs become one long line concatenated by "<br />", here is my solution.
New rss items will be formated properly. |
|
I've also reproduced this 1.2.3 release and Shrook RSS reader for Mac. The issue can be resolved by changing the string_api.php as follows: function string_rss_links( $p_string ) { rss can not start with which spaces will be replaced into by string_display().
} to function string_rss_links( $p_string ) { rss can not start with which spaces will be replaced into by string_display().
} The escaping of the RSS string is now only done in the MantisCoreFormatting rss() function, which looks as follows:
The question is whether we are fixing the formatting, but breaking some escaping logic or opening some security issue. |
|
Please see 0008539 as a related issue. Perhaps I forgot to fix up a usage of string_rss_links when committing those changes. Firefox seems to render the feed OK although it does place <br /> tags into the description which seems wrong to me (malformed XML). AFAIK Google Chrome/Chromium does not support RSS out of the box. You need a plugin to read RSS feeds in the browser. See http://code.google.com/p/chromium/issues/detail?id=84 Ideally I'd like to remove HTML tag processing support from MantisBT core as it makes the very wrong assumption that descriptions, comments, etc will always be rendered by software that interprets HTML. We have clients that communicate via SOAP and native operating system UIs. We send information to email clients that generally don't interpret HTML. We place information in RSS feeds. Twitter notifications. etc |
|
|
|
I know this is an old thread but the change to string_rss_links fixes the feed view in Thunderbird. |
|