Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (136 - 138 of 18300)

Ticket Resolution Summary Owner Reporter
#18802 duplicate dijit/Destroyable::own dies horribly if owning things without a cleanup method bill primejunta
Description

To reproduce:

  1. Create a widget or other Destroyable, and .own something without a ::remove, ::destroy, or ::destroyRecursive method
  2. Call that widget's ::destroy method

Expected: widget is destroyed, the .own'ed object is ignored Observed: the destroy sequence fails with "TypeError?: handle[destroyMethodName] is not a function."

Note: it kind of makes sense that it works like this, but breaks back-compatibility. I'm running into this issue when setting listeners on a third-party AMD module which has an ::on method which doesn't return an object with a ::remove method. When I set a listener with dojo/on, it gets delegated to the third-party, and I can't ::own the on as usual. So it would be nice if this was fixed; all it would take is changing line 54 in dojo/Destroyable to:

if(typeof handle[destroyMethodName] == "function") handle[destroyMethodName](preserveDom);

#18800 invalid Метод validate.check() всеп поля помечает как Invalid dylan victorynox
Description

Метод validate.check() все поля помечает как Invalid. Так как во время проверки корректности поля ожидается объект constraintResponse с полями isValid(bool), message(string), а методы проверки (validate.isText и подобные) возвращают true или false, в итоге проверяется constraintResponse.isValid который в свою очередь на самом деле является не объектом, а bool переменной

var constraintResponse;
			// case 1: constraint value is validation function
			if(lang.isFunction(profile.constraints[name])){
				constraintResponse = profile.constraints[name](elem.value);
			}else if(lang.isFunction(lang.getObject(name, false, profile.constraints))){
				// case 2: constraint value is validation function name as string
				constraintResponse = lang.getObject(name, false, profile.constraints)(elem.value);
			}else if(lang.isArray(profile.constraints[name])){

				// handle nested arrays for multiple constraints
				if(lang.isArray(profile.constraints[name][0])){
					for(var i=0; i<profile.constraints[name].length; i++){
						constraintResponse = validate.evaluateConstraint(profile, profile.constraints[name][i], name, elem);
						if(!constraintResponse.isValid){ break; }
					}
				}else{
					// case 3: constraint value is array, first elem is function,
					// tail is parameters
					if(lang.isFunction(lang.getObject(name, false, profile.constraints))){
							constraintResponse = validate.evaluateConstraint(profile, profile.constraints[profile.constraints[name]], name, elem);
					}else{
						constraintResponse = validate.evaluateConstraint(profile, profile.constraints[name], name, elem);
					}
				}
			}

			// if constraintResponse is false (backwards compatibility with last version) or if property isValid is false, return the invalid field name and/or the constraintResponse message
			if(!constraintResponse){
				invalid[invalid.length] = elem.name;
			}else if(!constraintResponse.isValid){
				invalid[invalid.length] = { field : elem.name, message : constraintResponse.message
#18799 fixed [regression] StackContainer: visibility:visible elements from unselected panes are visible bill gerhard presser
Description

I'm using the dojox/layout/GridContainer with Portlets.
the GridContainer? is nested into a dijit/layout/StackContainer.

if one switches from one visible tab to another, the CSS-classes dijitVisible/dijitInvisible are set on the nested containers.
since 1.11.0-rc1, these selectors use the visibility property instead of the display property.

this causes the portlets to remain visible, because they have their visibility set to 'visible'.

I'm not that familiar with the visibility property, but it seems there can be visible children, even if the parent is hidden.

environment: chrome 48.0.2564.116 m, dojo 1.11.0-rc1

Note: See TracQuery for help on using queries.