BlindRSS does not display the `<description>` field for feed items #33

New issue

Closed

opened 2026-06-30 06:05:58 -07:00 by serrebi · 4 comments

serrebi commented

2026-06-30 06:05:58 -07:00

Owner

Currently, when BlindRSS loads an RSS feed, the article list displays the following information for each item:

Title
Author
Publication date
Channel name
Read/unread status

By pressing Tab, the user can navigate to a read-only text field that shows the extracted text from the linked page.

However, RSS items often include a <description> element, which can serve as:

A full equivalent of the page text;
A snippet or excerpt of the page content;
An independent annotation or summary.

This <description> field frequently holds distinct informational value. Users would like to access its content while retaining the current functionality of viewing the extracted page text.

Desired behavior

Provide a way to view the content of the <description> field without losing the ability to see the extracted page text as implemented now.

Possible implementation approaches

Add a new column in the article list to display the <description> text.
Note: The description can sometimes be very long, so this may require visual truncation.
Introduce a per-channel setting to choose what is shown in the text preview area: either the extracted page content or the <description> field.
This would allow users to tailor the behavior per channel depending on which source of text is more useful for that specific feed.
Any alternative UX options

Acceptance criteria

Users can view the <description> field content for RSS items.
The existing ability to view the extracted page text remains available.
Any new UI elements do not break keyboard navigation (including Tab flow).
If a configuration option is implemented, it is per-channel and persists across sessions.
Long descriptions are handled gracefully (truncation, expandable text, or alternative presentation).

Currently, when BlindRSS loads an RSS feed, the article list displays the following information for each item: - Title - Author - Publication date - Channel name - Read/unread status By pressing `Tab`, the user can navigate to a read-only text field that shows the extracted text from the linked page. However, RSS items often include a `<description>` element, which can serve as: - A full equivalent of the page text; - A snippet or excerpt of the page content; - An independent annotation or summary. This `<description>` field frequently holds distinct informational value. Users would like to access its content while retaining the current functionality of viewing the extracted page text. #### Desired behavior Provide a way to view the content of the `<description>` field without losing the ability to see the extracted page text as implemented now. #### Possible implementation approaches 1. **Add a new column in the article list** to display the `<description>` text. *Note:* The description can sometimes be very long, so this may require visual truncation. 2. **Introduce a per-channel setting** to choose what is shown in the text preview area: either the extracted page content or the `<description>` field. This would allow users to tailor the behavior per channel depending on which source of text is more useful for that specific feed. 3. **Any alternative UX options** #### Acceptance criteria - [ ] Users can view the `<description>` field content for RSS items. - [ ] The existing ability to view the extracted page text remains available. - [ ] Any new UI elements do not break keyboard navigation (including `Tab` flow). - [ ] If a configuration option is implemented, it is per-channel and persists across sessions. - [ ] Long descriptions are handled gracefully (truncation, expandable text, or alternative presentation).

serrebi commented

2026-06-30 09:37:23 -07:00

Author

Owner

Fixed and released in v1.71.1. Changes: feed item descriptions are stored separately from extracted/full content when a feed provides a distinct description or summary; the article list now has a truncated Description column; the article context menu includes View Feed Description... for the full description in a read-only, keyboard-accessible dialog; existing extracted page text behavior remains unchanged. Verification: full test suite passed (929 passed, 7 skipped), build.bat release completed, and GitHub latest points to v1.71.1.

serrebi commented

2026-06-30 12:45:41 -07:00

Author

Owner

Overall, the implementation is as expected, but please implement closing the modal dialog window with the description display by pressing the Escape key.
Currently, this dialog does not close when pressing Escape key, and you must explicitly click the Close button.

Overall, the implementation is as expected, but please implement closing the modal dialog window with the description display by pressing the Escape key. Currently, this dialog does not close when pressing Escape key, and you must explicitly click the Close button.

serrebi commented

2026-06-30 13:45:40 -07:00

Author

Owner

Good catch — fixed. The Feed Description dialog now closes on Escape, same as clicking Close. Will go out in the next release.

Good catch — fixed. The Feed Description dialog now closes on Escape, same as clicking Close. Will go out in the next release.

serrebi closed this issue

2026-07-01 05:16:25 -07:00

serrebi commented

2026-07-01 05:16:25 -07:00

Author

Owner

Thanks! The issue is resolved and I’m closing it now.

Thanks! The issue is resolved and I’m closing it now.