Hi Dex,
after the old rendering engine was canceled a few days ago, it is quite up to date and CFS is missing. Missing A LOT! :-)
Any plan?

Thanks, Fajfka

Same under GreaseMonkey. :-(
Because Feedly unfortunately did make some changes to the old rendering engine. It would only be necessary for Dexmaster to rewrite the CFS for the new rendering engine.
Although he promised me in December '16 to look at it, he probably did not have time, or he not use Feedly now.

Re: @Dexmaster:
Hi, I even hope that you would do in the future even more focused. I was very pleasantly surprised your reaction. Big thanks!
F.

Hi Dexmaster.
Are you going to rewrite your great CFS to new React-base rendering engine? In the old engine, some things do not work properly in Feedly, but I still use old engine, bacause using the new engine without CFS almost not the point;-)
I would hope you find the time for editing your script again.

Thanks, F.

Re: @Dexmaster:
Great news, thanks Dexmaster.

And if the little script to favicons also had to determine its own favicon for the resource manually, it would be quite incredible - I read two sources which favicon is unfortunately missing .. it would be nice if all of the lines looked the same :-)

Re: @Dexmaster:
Many thanks for fixing slimFeed script. I had a few problems - it did not work with GreaseMonkey 3.1, I tried to delete GM and install Scriptish - also icons did not show. Then I changed GM to version 2.3 and with that already works. I tried to update again to GM 3.1 and script works so far.

But I would welcome another small adjustment in slimFeed, which I had forgot - odd or even row has a light green background color. Background color of each open cell is such - I think it would be appropriate to modify these lines in the script:

cssTxt += ".u0Entry:nth-child(even) { background-color:#f6fceb; } .u0Entry:nth-child(odd) { background-color:#f6fceb; }";
cssTxt += ".u4Entry:nth-child(even) { background-color:#f6fceb; } .u4Entry:nth-child(odd) { background-color:#fdfef9; }";
cssTxt += ".u5Entry:nth-child(even) { background-color:#f6fceb; } .u5Entry:nth-child(odd) { background-color:#fdfef9; }";
cssTxt += ".u100Entry:nth-child(even) { background-color:#f6fceb; } .u100Entry:nth-child(odd) { background-color:#f6fceb; }";

..in the past I've tried switch to a background-color:#f6fceb to background-color:#ffffff, but had only just suspect it was in rows u0 and u100, and it would be better to have it changed the author of modification, if you acknowledged that it is coloring even rows unnecessary or not very useful..

Big thanks, Fajfka

Just favicons :-)
Colors that were seen in the picture of my Feedly in another issue here is just kind of substitute for the favicons from a dysfunctional SlimFeed script.

Colors are from this script.

I once used except your CFS also another script (Feedly slimFeed) that artificially show favicons of the corresponding server, and when displaying the All view and view settings Title only, it was too handy.
But unfortunately this script does not work long time ago.
Would he tried you please draw inspiration from that script, and the same or similar function to offer in your amazing CFS?

Old script is here:
https://openuserjs.org/scripts/labm0nkey/Feedly_slimFeed
https://greasyfork.org/cs/scripts/846-feedly-slimfeed
..and here is script with picture of that function, some discussion about it, and some old versions:
http://userscripts-mirror.org/scripts/show/171435

Big thanks, Dexmaster!

some_cleening selection is cool, but when i have "Title only" and when it is in the channel display only a few unread articles, offsets the original Giant Mark as read button high into the site.
some-cleening

Hi Dexmaster. mark_all_fix originated in the past, at my request, thank you for that.
It would be possible to make its presentation to behave a little differently? Very fine for me it's a big button smaller than the original, and it is always at the bottom of the browser window, but in some occasions upset that is displayed at the same place every time, and in some cases that were not good, as shown in the preview :

Giant Mark all as read fixed
vs.
Giant Mark all as read original

Modified giant button takes up less space so that it's at the bottom, but otherwise, it would probably well to behave like the original button.
Yes, I know you there then added only another script recommended by me, but if you were his behavior, he managed to tweak a little bit, that would be great.. :-)

Big thanks, F.

Hi Dexmaster. mark_all_fix originated in the past, at my request, thank you for that.
It would be possible to make its presentation to behave a little differently? Very fine for me it's a big button smaller than the original, and it is always at the bottom of the browser window, but in some occasions upset that is displayed at the same place every time, and in some cases that were not good, as shown in the preview :

vs.

Modified giant button takes up less space so that it's at the bottom, but otherwise, it would probably well to behave like the original button.
Yes, I know you there then added only another script recommended by me, but if you were his behavior, he managed to tweak a little bit, that would be great.. :-)

Big thanks, F.