Firefox 用户 9786606 的评价
评分 4 / 5
来自 Firefox 用户 9786606，6 年前Very nice reader. There are a few things that are bugging me though (firefox 64.0 x32):
I have selected for it to show only unread messages, but when I mark an entry as read, it will not disappear until I reload the feed, folder or whatever. Is that intentional?
In the 5th view at least, clicking an article text will expand it, but clicking it again won't make it return to its original state. So depending on the feed I'm stuck with giant images. (e.g. http://www.computerbase.de/rss/news.xml)
Also, having a way to inject custom css and js would be nice.
I have selected for it to show only unread messages, but when I mark an entry as read, it will not disappear until I reload the feed, folder or whatever. Is that intentional?
In the 5th view at least, clicking an article text will expand it, but clicking it again won't make it return to its original state. So depending on the feed I'm stuck with giant images. (e.g. http://www.computerbase.de/rss/news.xml)
Also, having a way to inject custom css and js would be nice.
开发者回应
发布于 6 年前1. Yes it's intentional that items marked as read aren't hidden right away. This gives the user the possibility to "undo" the mark as read operation.
2. That's true. Note that you can collapse by pressing Enter but currently "closing by clicking" isn't supported. This is because closing isn't really needed and a careless attempt to click a hyperlink in the article could result in collapsing the article which could infuriate some users (we tested this :)).
3. Custom CSS support would be easy to implement but the CSS hasn't been very stable (we have changed it a lot along the way) which could easily lead to breaking custom CSS configs and an avalanche of support requests and complaints. So it hasn't been implemented so far. We are open to all UI improvement ideas though.
2. That's true. Note that you can collapse by pressing Enter but currently "closing by clicking" isn't supported. This is because closing isn't really needed and a careless attempt to click a hyperlink in the article could result in collapsing the article which could infuriate some users (we tested this :)).
3. Custom CSS support would be easy to implement but the CSS hasn't been very stable (we have changed it a lot along the way) which could easily lead to breaking custom CSS configs and an avalanche of support requests and complaints. So it hasn't been implemented so far. We are open to all UI improvement ideas though.