@Richman the default reader fixes nothing, it is a substitute, and a poor one at that. with the legacy reader, you had everything you needed
on the page, and instead of simply streamlining the reader sub-header and making it float like the site header does already, it's crammed to the side, and has the drop-down menu for pages turned into an obtrusive bar.
@RonBWL agreed.
@DLRevan @comeonnow0 this very thread shows that there's little to no communication between site operators, just look at the post
@Teasday made:
Yesterday I decided I was going to work on that as an option (since I've already made changes to that effect), I just wasn't expecting legacy to be killed while I was sleeping lol
i don't know what else you can call that. doesn't a project normally get everyone involved on the same page before doing something like this? wouldn't members of a project usually get the option Teasday claims to be working on done and roll that out
before getting rid of the other feature?
@ixlone no, i mean 'shove' as in if you have a tiny poverty-tier computer monitor like me, and if you expand the sidebar on a large image, the image gets crushed; scrolling doesn't change the image's size and, again,
this a problem that wasn't present on legacy reader. you keep going on an on to defend this decision when if, instead of saying 'oh yeah we're getting rid of legacy reader' as parts of other posts about other things buried in threads people do not read, then getting rid of it and replacing it with a bad alternative, you had gotten
@Teasday's option done (if it were to indeed look and function like legacy reader), rolled it out along with an announcement about it, made an announcement (possibly with 'ads' like on april fool's) about how legacy reader will be removed after such time, fix any further problems with default reader, then remove it after everyone switches, you wouldn't be getting as many posts like mine.
you had more than two years to do this, even with last year's craziness.