SmartRSS / Smart-RSS

RSS extension
MIT License
114 stars 16 forks source link

Unintuitive behavior of the March 1st version #219

Closed Qrox closed 1 year ago

Qrox commented 1 year ago
  1. For some reason, Chrome's March 1st update (2.24.0) automatically sets the "show only unread" option without telling the user, so it looks as if the feeds were removed.
  2. Upon selecting a feed, the read items are only shown if you click on the unread count on the right, which is rather unintuitive and confusing, and again, there is not indication of this change of behavior to the user, so they might again think that unread items were removed.
  3. If there is no unread items in a feed, you cannot even click the unread count to see the read items.

In case someone else also encounters the third problem: you can add this to the appearance - user css settings to show the unread counter so you can click it to see the full list:

:not(.has-unread) > .source-counter {
    visibility: visible;
    color: rgba(0, 0, 0, 0.2);
}
zakius commented 1 year ago

I'm sorry for the trouble. I'll take a look at these, that definitely wasn't intended. Do changing settings to your preferred work?

Qrox commented 1 year ago

Do changing settings to your preferred work?

Which settings do you mean? I fixed the first problem by changing it in the settings, but there doesn't seem to be any settings related to the second and third problems.

zakius commented 1 year ago

Okay, I see now, somehow partially implemented feature slipped through, but that doesn't explain why both of these settings were set to active for you. I'll upload version allowing you to change this setting right now, it should be available in extension repositories soon and here in a few minutes

QmwJlHuSg9pa commented 1 year ago

I just updated to Firefox AMO v2.25.0 (from v2.23.2). Not only was "Toggle show only unread" enabled, but so was "DEFAULT_TO_UNREAD_ONLY!". Also, "Invert colors" was set to "Yes". None of these were enabled beforehand.

zakius commented 1 year ago

I'll investigate the reason of switching some of boolean settings. I'm almost certain it comes from wrong interpretation of saved settings but I never experienced it while working on it myself