Custom Query (18300 matches)


Show under each result:

Results (34 - 36 of 18300)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#4661 patchwelcome should BOM be included in build output, resource files? Adam Peller Adam Peller

If all supported browsers support the Unicode Byte Order Mark (BOM) then we should consider putting it at the top of our build output. This may make UTf-8 more explicit on the page and reduce problems for the user.

A separate issue -- if all the necessary tools support the BOM (#1660, #2440), should we use it in generated dojo.cldr files and any other non-ASCII files, like nls resources?

#4694 patchwelcome Form: add support for isDirty() bill

Give Form an isDirty() method, similar to the isDirty method provided by datastore. Such a method could be used to determine whether to enable/disable buttons, or maybe to dynamically change the label on buttons, or to prompt user whether to discard any changes, etc.

Such a functionality should be accompanied by the possibility to reset the form (and not necessarily to the values the form was originally loaded with).

A simple take on this could be to give each form widget an own isDirty() method, and then add a Form.isDirty() that just loops over those. However, this is limited to scenarios where each form field is also a dojo widget.

Another more generic take, can be based on the dom element's default values, i.e. since form was "loaded" (not, unfortunately, since form was last "undirtied", e.g. re-instantiated with the values of another "item"). Some sample code for this variation is at:

A 3rd and maybe better approach, is to make the Form widget remember reference values for contained fields (whether dojo widgets or not) that an isDirty() method could check field values against. An unDirty() method should also be provided to reset the fields to these reference values (that may be different than the standard reset() method, that resets to default values when Form was loaded). Re-instantiating the form with the values of another "item" would therefore also reset the form's reference values.

See also: #4692

#4765 patchwelcome DateTextBox: support isDisabledDate guest

I'm trying to use dijit.DateTextBox to allow users to select dates, but I need to disable weekends. If I use dijit._Calendar, I can set myCal.isDisabledDate =, but that doesn't work for a DateTextBox.

In talking with peller about this in #dojo, it was mentioned that it might be possible to add another option on the constraints to handle this.


2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.