Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (103 - 105 of 18300)

Ticket Resolution Summary Owner Reporter
#16516 invalid Tree: items lost using DnD to reorder a node's children bill AlexG
Description

http://dojo-toolkit.33424.n3.nabble.com/dijit-Tree-DND-betweenThreshold-bug-please-help-td3992612.html

When dragging in a Tree item 1 before item 2, item 1 disappears somewhere, the same happens when dragging item 1 after item 2.

#18649 invalid Switching localization and Cookie plugin for enhanced grid Alex_IZA Alex_IZA
Description

Columns names are localized in grid. When user change the localization on web page, the name of grid columns is changed.

Module dojox/grid/enhanced/plugins/Cookie, in function “var _loadColumnOrder = function (colOrder, grid)”

It contains condition: if (json.toJson({'name': cell.name, 'field': cell.field}) == json.toJson(cellInfo)) {

if (cell.field == cellInfo.field) {

break;

}

Of couse the cell.name != cellInfo.name (from cookie), because the names of the current cell and the name of cell from cookie vary after user did switching localization.

Why not compare only cell.fields: if (cell.field == cellInfo.field) {

break;

}

And change function code _saveColumnOrder: return {

"name": cell.name, "field": cell.field

};

#9802 fixed intermediate accessible between grid and row containing header cell is created Becky Gibson Alexander Surkov
Description

URL: http://archive.dojotoolkit.org/nightly/dojotoolkit/dojox/grid/tests/test_data_grid.html

HTML div element with @id="dojoxGridMasterHeader" has @tabindex="-1" which makes it focusable and therefore it has accessible object even @role="presentation" is presented. This alters accessible of dojo grid:

grid

nothing

row

column header column header

expected accessible tree is

grid

row

column header column header

Accessible tree where intermediate accessible between grid and row accessibles is presented confuses Firefox and grid is not correctly exposed to screen readers.

Is there specific reason to make that DIV programmatically focusable which leads to accessible tree altering?

Note: See TracQuery for help on using queries.