Closed
Bug 554101
Opened 15 years ago
Closed 14 years ago
RSS feed item in non-feed folder doesn't show the article summary
Categories
(MailNews Core :: Feed Reader, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 522645
People
(Reporter: aryx, Unassigned)
References
Details
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 ThunderBrowse/3.2.8.1 Mnenhy/0.7.6.666
RSS feed item in non-feed folder doesn't show the article summary.
Steps to reproduce:
1. Create a Feed-Account.
2. Subscribe to a feed (here planet.mozilla.org) and set that the article summary gets loaded.
3. Select an item, see the summary.
4. Move the item to a mail folder (here: grandchild of the Local Folders' inbox)
5. Select the item.
Actual result: Nothing is shown.
Reproducibility always
Comment 1•14 years ago
|
||
Magnus would you have any interest in fixing this ?
Reporter | ||
Comment 2•14 years ago
|
||
This happens in Thunderbird 3.0.*, but not in SeaMonkey 2.0.*
Reporter | ||
Comment 3•14 years ago
|
||
The reason for this: The downloaded feed items are now encapsulated into a body tag with the attribute selected="false" and http://mxr.mozilla.org/comm-central/source/mail/themes/qute/mail/messageBody.css#154 adds the css property display:none. Altering selected to true fixes this (as would removing the CSS rule).
Can someone explain why the code has been changed to this?
Comment 4•14 years ago
|
||
(In reply to comment #3)
> The reason for this: The downloaded feed items are now encapsulated into a body
> tag with the attribute selected="false" and
> http://mxr.mozilla.org/comm-central/source/mail/themes/qute/mail/messageBody.css#154
> adds the css property display:none. Altering selected to true fixes this (as
> would removing the CSS rule).
>
> Can someone explain why the code has been changed to this?
How would you feel about creating a patch for this ?
Comment 5•14 years ago
|
||
(In reply to comment #3)
> The reason for this: The downloaded feed items are now encapsulated into a body
> tag with the attribute selected="false" and
> http://mxr.mozilla.org/comm-central/source/mail/themes/qute/mail/messageBody.css#154
> adds the css property display:none. Altering selected to true fixes this (as
> would removing the CSS rule).
>
> Can someone explain why the code has been changed to this?
It's used to choose between the summary vs. the displaying the article as a web page. SeaMonkey has exactly the same rules.
Reporter | ||
Comment 6•14 years ago
|
||
Ludovic: As long as I don't know and understand the concept behind the changes in Thunderbird 3 causing this, I can't write a patch.
Magnus: I haven't investigated SeaMonkey (2.0.8) further as the problems doesn't occur there, probably because of the use of the old header view (or maybe blocking remote content).
Reporter | ||
Comment 7•14 years ago
|
||
Thunderbird works as expected until 2009-06-06. The 2009-06-07 build doesn't even show the feed summary for feed items in a feed account. Reason for this probably: http://hg.mozilla.org/releases/comm-1.9.1/log/22248bfae2b7
2009-06-12 builds show this bug here (bug 554101), I haven't tested the builds between.
So has http://hg.mozilla.org/releases/comm-1.9.1/log/22248bfae2b7 caused this bug or the fix for not showing the summary has fixed it only in feed accounts?
Blocks: 496626
Reporter | ||
Comment 8•14 years ago
|
||
Seems like from 2009-06-05 to 2009-06-12, you need to restart Thunderbird after downloading feed items with feed summary view to read them. This is fixed in 2009-06-13 and starting with this nightly, the feed summary view doesn't work anymore for local folders.
Reporter | ||
Comment 9•14 years ago
|
||
Andrew, have you any clue if this is/can be a regression from the gloda mega-bug which has been checked in on 2009-06-12? Thanks.
Comment 10•14 years ago
|
||
Very likely. I think I recall commenting on a bug along these lines previously (move RSS item to non-RSS folder, no longer seen as RSS), so there's dupe-fodder out there.
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•