version 1115 change in feed list layout
![]() ![]() |
Dear Dustin, The 1105 version has changed the way the list of feeds is displayed. Here is how it looks for me in version 1104: http://i40.tinypic.com/xomfs8.png
Is there a way for me to bring back the previous layout by entering custom css? Thanks!
|
![]() |
I just uploaded a new version. Try it out and see if that fixes your problem. |
![]() |
even with the latest version just uploaded. a lot of my feeds still have ellipses. FF8 |
![]() |
@DarKHelmeT: But do they go to the edge of the side nav area? |
![]() |
negative.
|
![]() |
@DarKHelmeT: That looks like what I'd expect. The extra space is reserved for the scroll bar and the maximum width of the unread title count. Previous versions of this script would crop off the unread count for long folder/feed names. If that's acceptable behavior, you can just turn off the unread counts from the drop-down menu in the subscriptions area to allow the titles to take up the maximum amount of space. If that's not enough, here's some custom CSS to push the titles to the extreme:
|
![]() |
that css looks good for most of the feeds.. any way to go a little more extreme to force the unread count to align to the Titles and ignore the margin? sorry for being so picky XD
|
![]() |
@DarKHelmeT: I'm not 100% sure what you mean by "align to the Titles and ignore the margin" in your request. Below is some code that you can add to the previous code to ensure the unread counts aren't obscured by long feed titles. Unfortunately this doesn't mimic the default behavior where the unread count is placed directly to the right of shorter feed names -- all unread counts are right justified. Also, this assumes you're not applying any scripts that change colors, as the background for the unread counts is changed to white in order to prevent it from overlapping the feed title. Due to the fact that the width of the unread count element is variable, I think that's the best that can be done.
|
![]() |
what i meant was that, by default, the counts sit right next to the title. but with long title names, they seem to hit a wall and get held back and therefore get stepped on by the Titles. i just want to have the counts ignore that wall..if they get cut off, then thats when i can extend the margin size. just want the titles and counts to act as if they have all the space in the world ;) |
![]() |
OK… I think I understand now. This code will make the title use up all the space and only display the unread count if there's enough room.
|
![]() |
overflow + max-width css makes it perfect! thanks much. |
![]() ![]() |
Thank you Dustin, that's exactly what i wanted (the last custom css).
|
![]() |
Yay Dustin. That CSS makes everything better. The latest updates really made the whole experience quite ugly and unpleasant. But this css makes everything usable again. |
![]() |
To be honest, I best liked the version from Nov, 15 |
![]() |
I'm very interested by the feedback on this change. I was fixing what I saw as a bug: very long folder/feed names caused the unread count to be hidden. The latest version of the script restores the default (Google) way of dealing with long names while still taking up as much of the side nav element as possible. The entire width can be used by hiding the unread counts on all items. I took an all or nothing approach that either unread counts should always be visible or never be visible, but it seems like the consensus is that unread counts should be visible on items where they can fit next to the name, but that if the name is too long, it's OK to hide the unread count. I'm currently coding in an option where the default (checked) behavior implements the last piece of CSS I posted. Can anyone help me think of a good descriptive name for this option that's not too long? Maybe, "Maximize navigation title lengths"? |
![]() |
@SilverSurfer- The version from the 15th had an awful lot of dead space to the right of the feed titles. This caused many more feed names to be cropped than should have been. The version from the 17th (current version) took back most of that space. |
![]() |
Sorry, my mistake: I best liked the version up and until before the changes on Nov, 15 |
![]() |
Re: "I'm currently coding in an option..."
|
![]() |
@SilverSurfer- There shouldn't be any difference between 1 & 3. Is the "medium size margin" in #1 referring to the right margin as seen in http://i41.tinypic.com/2ls7mh.png? Unless my brain is totally scrambled at this point, the 3 different behaviors are as follows: 1) Maximum title length [build <= 1104]
I'm going to keep the option to 1 & 3 because #2 doesn't remove white space, it just shifts the navigation tree to the left. |
![]() |
Please mind the space requirement also depends on user preferences. We have 4 different situations:
Probably my mind is scrambled, since I "remembered" this:
|

