Post

8 followers Follow
12

Search Disappears when scrolling through list pane

When I scroll down through a list pane, the ndWeb window moves up to hide everything above the blue toolbar.  I then have to scroll back up to the top to access Search.  

When Search was ON the blue toolbar, this was not a problem.  

Search should always be visible.

It would also be nice to have a quick easy way to GoToTop, after scrolling down.  

 

Status: None

Please sign in to leave a comment.

5 comments

1
Avatar

Also, if you try to use the scroll bar and manually click and drag your list back to the top, the search bar does not come back.  You have to use the scroll wheel on your mouse which sometimes can take a while, depending on how far down people have scrolled.

1 vote
1
Avatar

The functionality to pin the search bar is required in our firm as well. Search needs to always be accessible. Not sure why Search is not considered part of the power bar. Please note Search features must be set up to remain available in List and Summary View. In IE11, the Home keyboard button works in Summary View but not in List View past the first page of rows.

1 vote
1
Avatar

Users are complaining in 17.2 that when they scroll the upper portion of the window disappears. I had hoped this would be fixed in 18.1. Unfortunately, I saw in the 18.1 Beta group that ND considers this to be a feature to give people more "screen real estate".

If you want users to have more screen real estate, perhaps give the user a choice similar to how Microsoft allows people to show/hide the Ribbons in their Office apps.

If a user has scrolled down far enough, they lose the ND logo, Search, Add options and they have to press F5 to refresh and get it back. This really is not a "feature" when someone has to press F5 to refresh a window to get back tools they need.

Users were hoping this would be resolved in 18.1 since this has been a problem for us with 17.2.

Yes, I added this to the Beta testing page and as a ticket, but this continues to be a bug. Please fix this.

1 vote