Issue 33756 in chromium: The last dev version for Mac OS has problem with RSS feeds.
chro...@googlecode.com
Owner: ----
Labels: OS-Mac Area-Undefined Pri-2 Type-Bug
New issue 33756 by ikaprik: The last dev version for Mac OS has problem
with RSS feeds.
http://code.google.com/p/chromium/issues/detail?id=33756
Chrome Version : 5.0.307.1 dev
URLs (if applicable) :http://avs-galary.ru/feed/
http://www.engadget.com/rss.xml
http://www.autoblog.com/category/timewarp/rss.xml
OS version : Mac OS 10.6.2 Snow Leopard
Behavior in Safari 3.x/4.x (if applicable): Feeds are indicated properly
Behavior in Firefox 3.x (if applicable): Feeds are indicated properly
Behavior in Chrome for Windows: Feeds are indicated properly
What steps will reproduce the problem?
1.Every feed I`ve tried to see didn`t indicated
2.
3.
What is the expected result?
To indicate all the feeds properly, like Safari, Firefox and Opera do.
What happens instead?
U can see only symbols without design, format, structure and etc. It`s
indicating like a massive
text.
Attachments:
Rss bag.tiff 811 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
chro...@googlecode.com
Status: Duplicate
Mergedinto: 434
Comment #1 on issue 33756 by stuart...@chromium.org: The last dev
version for Mac OS has problem with RSS feeds.
http://code.google.com/p/chromium/issues/detail?id=33756
(No comment was entered for this change.)
chro...@googlecode.com
Labels: -OS-Mac -Area-Undefined OS-All Area-Feature
Mergedinto: 33181
Comment #2 on issue 33756 by d...@chromium.org: The last dev version for Mac
OS has problem with RSS feeds.
http://code.google.com/p/chromium/issues/detail?id=33756
See http://code.google.com/p/chromium/issues/detail?id=84#c149 for details:
"The RSS Subscription Extension by Google
https://chrome.google.com/extensions/detail/nlbjncdgjeocebhnmkbbbdekmmmcbfjd
implements reading RSS feeds.
Those of you who would like to follow the discussion on implementing this
natively in
Chrome (doing away with the extension) I suggest you star issue 33181."