Using Reader this afternoon, I noticed that the "n" and "p" keys, used
to scan down and up through the posts in list view, now causes the
selected post to move to the top of the view's window whenever
pressed. Prior to this, the displayed posts did not move, allowing
movement through the displayed posts.
Is this a trial change, or a permanent alteration?
If Google is interested in feedback on this change, mine would be
entirely negative. I'd like to retain control of which posts I see as
I navigate through my posts, without having it auto-scroll me.
If this is something I've accidentally switched to, could someone
please tell me how to restore the original behaviour?
I noticed this too, and ditto on the negative comment. I will visually
scan a page of news items, using 'n' and 'p' as a sort of cursor as
I'm moving. However, it's now almost impossible to do that, because
the whole list moves everytime I press one of those keys.
> Using Reader this afternoon, I noticed that the "n" and "p" keys, used
> to scan down and up through the posts in list view, now causes the
> selected post to move to the top of the view's window whenever
> pressed. Prior to this, the displayed posts did not move, allowing
> movement through the displayed posts.
> Is this a trial change, or a permanent alteration?
> If Google is interested in feedback on this change, mine would be
> entirely negative. I'd like to retain control of which posts I see as
> I navigate through my posts, without having it auto-scroll me.
> If this is something I've accidentally switched to, could someone
> please tell me how to restore the original behaviour?
> I noticed this too, and ditto on the negative comment. I will visually
> scan a page of news items, using 'n' and 'p' as a sort of cursor as
> I'm moving. However, it's now almost impossible to do that, because
> the whole list moves everytime I press one of those keys.
> Please make this an option that can be set!
> On Sep 24, 1:52 am, Jason Etheridge wrote:
> > Using Reader this afternoon, I noticed that the "n" and "p" keys, used
> > to scan down and up through the posts in list view, now causes the
> > selected post to move to the top of the view's window whenever
> > pressed. Prior to this, the displayed posts did not move, allowing
> > movement through the displayed posts.
> > Is this a trial change, or a permanent alteration?
> > If Google is interested in feedback on this change, mine would be
> > entirely negative. I'd like to retain control of which posts I see as
> > I navigate through my posts, without having it auto-scroll me.
> > If this is something I've accidentally switched to, could someone
> > please tell me how to restore the original behaviour?
> Using Reader this afternoon, I noticed that the "n" and "p" keys, used
> to scan down and up through the posts in list view, now causes the
> selected post to move to the top of the view's window whenever
> pressed. Prior to this, the displayed posts did not move, allowing
> movement through the displayed posts.
> Is this a trial change, or a permanent alteration?
> If Google is interested in feedback on this change, mine would be
> entirely negative. I'd like to retain control of which posts I see as
> I navigate through my posts, without having it auto-scroll me.
> If this is something I've accidentally switched to, could someone
> please tell me how to restore the original behaviour?
One more vote to return to how it was before, or at least provide the
user a way to set a default. I'm really used to moving my 'cursor'
without moving the whole list.
Thanks for your feedback on the recent changes we've made. We've heard
you loud and clear and will be reverting the "N" and "P" keyboard
shortcuts to their prior behavior later today. Thanks again for your
patience and for helping make Reader better!
> Thanks for your feedback on the recent changes we've made. We've heard
> you loud and clear and will be reverting the "N" and "P" keyboard
> shortcuts to their prior behavior later today. Thanks again for your
> patience and for helping make Reader better!
> This change should now be live, sorry again for the inconvenience.
> Mihai Parparita
> Google Reader Engineer
> On Sep 24, 2:41 pm, Google Reader Guide wrote:
> > Hi everyone,
> > Thanks for your feedback on the recent changes we've made. We've heard
> > you loud and clear and will be reverting the "N" and "P" keyboard
> > shortcuts to their prior behavior later today. Thanks again for your
> > patience and for helping make Reader better!
> Thank you!!!!
> That is so cool that you responded to us and fixed it in days. This
> is why I love Google!!
> On Sep 24, 8:05 pm, Mihai P. wrote:
> > This change should now be live, sorry again for the inconvenience.
> > Mihai Parparita
> > Google Reader Engineer
> > On Sep 24, 2:41 pm, Google Reader Guide wrote:
> > > Hi everyone,
> > > Thanks for your feedback on the recent changes we've made. We've heard
> > > you loud and clear and will be reverting the "N" and "P" keyboard
> > > shortcuts to their prior behavior later today. Thanks again for your
> > > patience and for helping make Reader better!
|
