What?
Very fine grained request. Most of our users don't even know about the ADO to ADO AJAX (views <-> html data properties <-> Viewers) nor that we override Drupal's AJAX (which has so many issues) Controller with our own implementation.
Right now, there is a JS action that triggers an AjAX Command (scroll up) when a view is loaded dynamically && has a pager(even if not used). Our interactions tap in between but eventually call the Drupal AJAX mechanic, so that Command could be triggered.
The idea would be to add an extra setting (like the one we have that allows us to skip setting the URL on an AJAX call) that allows a specific view to not call scroll up at all. Maybe? even a CSS selector option so the scroll-up could also be defined to scroll just to a certain part?
Very niche
What?
Very fine grained request. Most of our users don't even know about the ADO to ADO AJAX (views <-> html data properties <-> Viewers) nor that we override Drupal's AJAX (which has so many issues) Controller with our own implementation.
Right now, there is a JS action that triggers an AjAX Command (scroll up) when a view is loaded dynamically && has a pager(even if not used). Our interactions tap in between but eventually call the Drupal AJAX mechanic, so that Command could be triggered.
The idea would be to add an extra setting (like the one we have that allows us to skip setting the URL on an AJAX call) that allows a specific view to not call scroll up at all. Maybe? even a CSS selector option so the scroll-up could also be defined to scroll just to a certain part?
Very niche