Custom Query (18300 matches)


Show under each result:

Results (64 - 66 of 18300)

Ticket Resolution Summary Owner Reporter
#18906 fixed Can no longer set a DOM node as the target of a Standby dylan jandockxppw

In commit, which is intended to fix #16544 (enhancement), a setter for target is introduced. This setter selects a DOM node as target, given a string as dijit registry id or element id, if the setter argument is a string.

Note that there is no else branch. For any other type of argument, we now do nothing, silently!

Originally, setting the target of Standby required passing a DOM node, and we have code that does that. Now, that doesn't work anymore. We get an error on "show", because there is no target, although we did call set("target", node).

I believe that this cannot have been the intention. There should be an else branch that just sets the target if the argument is not a string, at least.

#18903 fixed dijit/CalendarLite does not accept January 1, 1970 00:00:00 as a valid date Michael Van Sickle <[email protected]…> Neil Roberts

When converting a number to a date, dijit/CalendarList uses the following logic:

	value = new this.dateClassObj(value);
	value.setHours(1, 0, 0, 0);

This prohibits January 1, 1970 00:00:00 from being used, as its timestamp is 0.

#18902 fixed Theme build process dylan dylan

As per #18536, there's an issue with builds when including the theme package. One approach is to add themes to the fixedScopeMap, but then it requires the presence of the themes package. So we need a solution that handles optional packages as part of the build process.

Note: See TracQuery for help on using queries.