Kat 的评价
评分 4 / 5
来自 Kat,7 年前Hello.
I like your extension. It replaces my old one and is visually very appealing. But I have a major problem, so I can't give you 5 Starts yet.
I can't seem to select particular feed entries and mark them as read OR unread. Somehow my feeds got marked as read (I think I figured out why) but I've not read half of them yet. So I wanted to select a batch of feed entries and mark then unread but it's impossible. I can not click on the feeds without extending them (a manual "extend", "collapse" function for each entry would be great for the views where there feeds are not extended by default) and can't select multiple entries either. Apparently I couldn't find even a mass "mar unread" option. :'D
I'd be very grateful if you fix this!
You might want to change keys, too, or allow their adjustment. Because when I type "m" to mark as read/unread for a single thread, firefox starts the in-site search function. Since this has been bugging me anyways I've removed that function in the configurations but I doubt that most users will do that
===========
EDIT as Reply to creator's reply: Yes I adjusted how the articles are markd as read. Still it'll be important to allow the selection of several articles to mark or unmark them.
Regarding the search bar: No it was set like that by default in the Firefox Quantum build. But then again it was synchronised with my old Profile so who knows X'D. Anyways "accessibility.typeaheadfind" was set on "true" instead of "false" in "about:config" ig´f anyone ever has the same problem. It's gone now so if it's just a bug on my side and no problem for others then that's great!
I like your extension. It replaces my old one and is visually very appealing. But I have a major problem, so I can't give you 5 Starts yet.
I can't seem to select particular feed entries and mark them as read OR unread. Somehow my feeds got marked as read (I think I figured out why) but I've not read half of them yet. So I wanted to select a batch of feed entries and mark then unread but it's impossible. I can not click on the feeds without extending them (a manual "extend", "collapse" function for each entry would be great for the views where there feeds are not extended by default) and can't select multiple entries either. Apparently I couldn't find even a mass "mar unread" option. :'D
I'd be very grateful if you fix this!
You might want to change keys, too, or allow their adjustment. Because when I type "m" to mark as read/unread for a single thread, firefox starts the in-site search function. Since this has been bugging me anyways I've removed that function in the configurations but I doubt that most users will do that
===========
EDIT as Reply to creator's reply: Yes I adjusted how the articles are markd as read. Still it'll be important to allow the selection of several articles to mark or unmark them.
Regarding the search bar: No it was set like that by default in the Firefox Quantum build. But then again it was synchronised with my old Profile so who knows X'D. Anyways "accessibility.typeaheadfind" was set on "true" instead of "false" in "about:config" ig´f anyone ever has the same problem. It's gone now so if it's just a bug on my side and no problem for others then that's great!
开发者回应
发布于 7 年前Thank you for your review!
Please open Options page. There you can select how articles are marked as read. Default is when the title of the article is shown (quite "eager" mode), another option is when the bottom of the article is shown (requires that you expand articles and scroll to the end) or manually by unchecking "keep unread" checkbox or by pressing 'm'.
Edit: Feedbro 3.35.0+ fixes the keyboard shortcut issue you mentioned.
Please open Options page. There you can select how articles are marked as read. Default is when the title of the article is shown (quite "eager" mode), another option is when the bottom of the article is shown (requires that you expand articles and scroll to the end) or manually by unchecking "keep unread" checkbox or by pressing 'm'.
Edit: Feedbro 3.35.0+ fixes the keyboard shortcut issue you mentioned.