You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ui-grid is just one of the components on our page (could even be more then 1 ui-grid)
but we do call focus() on a certain element, but the focus is then most of the times (depends on timing) suddenly transferred .
Its then on the div with the class "ui-grid-focuser" this is because in cellnav.js on line 851 there is always a focus request call: uiGridCtrl.focus();
ui grid should not do that by default when it is constructed, only when it somehow already had focus or focus was request to it by the developer itself.
Now the focus is really forced to it when loading (and for me at that time the grid is even not filled its empty)
The text was updated successfully, but these errors were encountered:
As you navigate the grid using cell nav the browser should now read out
the cell that is currently focused.
Fixesangular-ui#3896
Partially angular-ui#3815
As you navigate the grid using cell nav the browser should now read out
the cell that is currently focused.
Fixesangular-ui#3896
Partially angular-ui#3815
As you navigate the grid using cell nav the browser should now read out
the cell that is currently focused.
Fixesangular-ui#3896
Partially angular-ui#3815
ui-grid is just one of the components on our page (could even be more then 1 ui-grid)
but we do call focus() on a certain element, but the focus is then most of the times (depends on timing) suddenly transferred .
Its then on the div with the class "ui-grid-focuser" this is because in cellnav.js on line 851 there is always a focus request call: uiGridCtrl.focus();
ui grid should not do that by default when it is constructed, only when it somehow already had focus or focus was request to it by the developer itself.
Now the focus is really forced to it when loading (and for me at that time the grid is even not filled its empty)
The text was updated successfully, but these errors were encountered: