Custom Query (18300 matches)

If you navigate to this page: ​http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Select.html with JAWS and tab into the first dijit.form.Select dijit, JAWS does not read the first selected option. For example, JAWS will say "Test one colon list box collapsed" - it should read out "Virginia." The reason for this is that the "aria-selected" attribute is not applied to the <span> with role="option". Interestingly, when the user activates the listbox, dijit creates a new drop down with all of the available options and correctly applies aria-selected attribute, which is why JAWS will read the options as you scroll through.

The fix is to just apply aria-selected to this initial DOM node.

dijit._HasDropDown exposes methods to open and close a popup containing the dropDown content. These methods delegate to the popup manager. When a _HasDropDown instance is being destroyed, it should help the popup manager to remove its own references on this disappearing _HasDropDown.

An use-case of this is Single Page Applications.

But also, more generally, just the simple case of destroying such a _HasDropDown instance should notify the popup manager about its destruction simply in order to avoid to keep dead references.

Another a warning : Here we met another problem with a child class. I did not check whether this problem occurs on pure Dojo components : When opening a new DropDown?, the previous popup on the stack is processed (closing, properties change, ...). But data of the previous popup is now incomplete and produce an error in the following lines :

onClose: function(){

domAttr.set(self._popupStateNode, "popupActive", false); domClass.remove(self._popupStateNode, "dijitHasDropDownOpen");

self._set("_opened", false); use set() because _CssStateMixin is watching

}

because self._popupStateNode is null now.

An simple idea to solve this : dijit._HasDropDown.destroy() should call "this.closeDropDown()".

Hope that it helps.

Regards

On api.dojotoolkit.org:

1) click the plus sign next to "dijit" 2) click in the pane on the right 3) scroll the tree down using the scroll bar 4) click the plus sign next to "registry"

At this point the Tree scrolls to the top again.

Happens at least on chrome, and apparently it's related to the Tree.focus() method itself, which is getting called when you click the plus sign next to "registry".