With JS enabled, the entire Views table is rebuilt, and the cursor is moved to the top of the page.
Splitting off from.
I can imagine you might want to move the cursor along with the view you enabled because you are likely wanting to edit it further. When disabling a view you might want to stay in the enabled views list because you don't want to do anything further with the disabled view. That would mean that the cursor would always end up somewhere in the enabled views listing. Makes sense?
Why this should be an RC target
Without this patch, using Views will be more difficult as a screen reader users or a keyboard only users . Predictability is really important for blind users and having the cursor location move unexpectedly can be a major disruption.
RC phase evaluation
|Issue category||Bug because the expected behavior is to keep the focused element|
|Issue priority||Normal because it only affects a really small percentage of users|
|Needed in RC||The main goal of this issue is accessibility. (Reduces screen readers pain using the Drupal interface)|
|Disruption: Fixes a bug, blocks a contributed project, or should be backported to Drupal 7||Not disruptive as it takes care to do nothing in the case the focus were called by the ajax response on purpose.|