Revert "remove obsolete dijitBorderContainerNoGutter and dijitBorderContainerNoGutterPane classes, refs #17966"
Turns out they weren't obsolete after all.
See the "gutters=false" example in test_BorderContainer.html and notice
the padding just inside the BorderContainer's border.

This reverts commit adfcd3bd30fae997a8cb8a3891b8c5aa324f1c76.
Fixes #18097.
Remove debugging console.log() from, fixes #18120.
It snuck into the code in 333e91c3a622eb8e123bb1bcf04494df610a22ad.
Clarify doc about BorderContainer.design vs. a child's layoutPriority.
Fixes #18138.
Use dojoClick=true for all clickable things in the Calendar,
including the drop down, for responsiveness and to fix #18140.

Still leaves the underlying problems that dijit/popup is calling
preventDefault() on the touchend event, thus canceling the click event,
and that (canceling out the first problem), dojo/touch is ignoring the
call to preventDefault().

Fixes #18140, refs #18150.
Use dojoClick=true for all popups, to make sure they get click events on iOS,
even though we are calling evt.preventDefault().  Avoids potential problems on iOS,
although it probably doesn't affect dijit's widgets directly because they already use
dojo/touch.

Refs #18150 and tangentially refs #18140.
HasDropDown: don't lose pointer to mouseup listener
when two mousedown events occur in a row.

Not feasible to test this via robot since it requires rapid right-and-left
clicking but see #18094 for test case.

Fixes #18094.
Rework menu test file to avoid spurious error on IE.

Closing the programmatic context menu tries to refocus the element that previously had focus,
which is likely the "create programmatic menu" button.  However, since that button disables itself
on click, it cannot be refocused.

Fixes #18167.
CalendarLite firstDayOfWeek option.
Fixes #18172.
trim trailing whitespace, refs #18172 tangentially
fix another test typo, refs #11132
fix case of path, refs #9575
(fixes typo from c973939b549322652ce31384e2f85c089e361493)
The compare() implementation for _DateTextBox was not doing a true-to-the-instance
value comparison, thus breaking the round trip. The solution was to fix the compare() method so that:

val = new Date(); // (or whatever)
widget.set('value', val);
rVal = widget.get('value');
widget.compare(val, rval) == 0;

Along with this fix is a regression test to ensure the round trip for TimeTextBox's continues to work.

Fixes #18201

Fixes regression from f018c601b407592956dd56cd41a5edfe332d55d2, refs #17955.
Make example subclassed TitlePane keyboard accessible,
to avoid spurious accessibility bug reports, refs #5973.

(cherry picked from commit de51ac6211202d9066315ce7313b0cb2ed36598f)
CheckedMenuItem: fix checkmark in high contrast mode.
Fixes #18229.

Fixes regression from 3365a6d (refs #17286), although I suppose
the real error is in the CheckedMenuItem template rather than 3365a6d.
Do not fire change events when ToggleButton/CheckBox/etc. do not actually change

Fixes #18232.
Fix additional document.domain editor edge cases

Refs #17529.
Fix _DateTimeTextBox missing params issue.

If a _DateTimeTextBox (DateTextBox or TimeTextBox) instance is created
without any parameters passed, an error is thrown because `params` is
assumed to exist.

Fixes #18243.
Allow specifying the start and end of the visible range in the picker.
Adds new pickerMin and pickerMax properties to _TimePicker, which can
be set indirectly through the TimeTextBox via the constraints property.

Also a lot of general cleanup of comments etc.

Based partly on original patch from Joerg Sonnenberger, thanks!

Fixes #18200.