Re:ReactOS was selected for Google Summer of Code 2016
by ank_the_elder on Monday February 29, 2016 @11:35PM
(#11200806)
So many mobile sites implement this same unpleasant UI control where the header follows your scrolling and stubbornly takes a portion of the screen without adding any useful functionality, that I wonder if people know it's possible to scroll to the top of any page and see the header there...
[ Parent
| on HN ]
Re:ReactOS was selected for Google Summer of Code 2016
by visarga on Tuesday March 01, 2016 @02:02AM
(#11201180)
<rant>I also object to menus that hide when scrolling up and show when scrolling down. I usually place the row I am reading at the top of the window to make it easier to follow visually. When I need to scroll back a little, the pesky menu comes out instead of the text. I think scroll up should be the exact inverse of scroll down, not a menu display trigger. Or, at least, offer us a few lines back scroll before showing the damn menu.
Re:ReactOS was selected for Google Summer of Code 2016
by willlma on Tuesday March 01, 2016 @03:20AM
(#11201411)
> at least, offer us a few lines back scroll before showing the damn menu
This
Re:ReactOS was selected for Google Summer of Code 2016
by umut on Tuesday March 01, 2016 @07:22AM
(#11202156)
I dont agree that you can kill me. At least cut a few fingers off, before killing.
^^ No, not this
Re:ReactOS was selected for Google Summer of Code 2016
by happyslobro on Tuesday March 01, 2016 @04:49AM
(#11201743)
I tried to explain the retardedness of this to management, before it was implemented. They were like "but people share more when the widgets are always visible, we A/B tested this!" It's like talking to a rock sometimes.
Re:ReactOS was selected for Google Summer of Code 2016
by userbinator on Tuesday March 01, 2016 @07:00AM
(#11202096)
That's like saying "but people click the ads more when they're obscuring most of the page or right next to the download button." They certainly do. Whether they intended to, however, is a different matter.