Date Range
<et2-date-range> | Et2DateRange
Choose a start and end date, either as two dates or as a named relative period The value is an object with
from and to. With relative the user instead picks a named period such
as “This month”, and the widget resolves it to concrete dates on read. (The previous text here described
Et2DateDuration - a different widget - and was what the generated documentation showed as this one’s
description.)
Examples
et2-date-range is a from/to pair in one widget - the “between these two dates” filter at the
top of a list. It has two quite different modes, and relative picks between them:
-
absolute (the default): two
et2-datefields, and the value is an object{from, to}. -
relative: one selector of named periods, and the value is the name -
"This week". The dates it means are worked out fresh every time, which is the point: a saved favourite holding"This week"still means this week next month.
See Which date widget for the rest of the family.
Like the other editable date widgets, value is set as a property rather than an attribute: in a
template the value arrives from the server, and in plain HTML like the examples below it is set from script
once the widget is ready.
Two dates
Both ends are ordinary date fields, so each is optional - a range with only a from is
“everything since”. With neither end filled in the whole value is null rather than an object of
empty strings.
Value: -
<et2-date-range id="range-absolute" label="Between"></et2-date-range>
<p>Value: <span id="range-absolute-out">-</span></p>
<script>
const rangeAbsolute = document.getElementById("range-absolute");
const rangeAbsoluteOut = document.getElementById("range-absolute-out");
const showRangeAbsolute = () => {rangeAbsoluteOut.textContent = JSON.stringify(rangeAbsolute.value);};
rangeAbsolute.addEventListener("change", showRangeAbsolute);
customElements.whenDefined("et2-date-range")
.then(() => rangeAbsolute.updateComplete)
.then(() => {rangeAbsolute.value = {from: "2026-03-01T00:00:00Z", to: "2026-03-31T00:00:00Z"};})
// the value is read back out of the two date fields, so they have to have rendered it first
.then(() => rangeAbsolute.fromElement.updateComplete)
.then(showRangeAbsolute);
</script>
A named period
relative swaps the two fields for a list of periods: today, yesterday, this and last week, this
and last month, the last three months, this and last year. The value is the name that was picked.
Value: -
<et2-date-range id="range-relative" label="Period" relative></et2-date-range>
<p>Value: <span id="range-relative-out">-</span></p>
<script>
const rangeRelative = document.getElementById("range-relative");
const rangeRelativeOut = document.getElementById("range-relative-out");
const showRangeRelative = () => {rangeRelativeOut.textContent = JSON.stringify(rangeRelative.value);};
rangeRelative.addEventListener("change", showRangeRelative);
customElements.whenDefined("et2-date-range")
.then(() => rangeRelative.updateComplete)
.then(() => {
rangeRelative.value = "Last month";
showRangeRelative();
});
</script>
What a named period actually covers
absoluteValue resolves the name against today’s date and hands back the same
{from, to} object the absolute mode produces. That is what you query with;
value is what you save. On an absolute range the two are already the same thing, so this only
matters in relative mode.
Every period is a whole one. “Last month” is the whole of last month, not the last thirty days, and it ends on that month’s own last day whether that is the 28th or the 31st. The one exception is “Last 3 months”, which runs to the end of the current month - it is three whole calendar months counting this one, not three months ending last month.
Pick a different period to see what it resolves to.
value: -
absoluteValue: -
<et2-date-range id="range-resolved" label="Period" relative></et2-date-range>
<p>value: <span id="range-resolved-value">-</span></p>
<p>absoluteValue: <span id="range-resolved-out">-</span></p>
<script>
const rangeResolved = document.getElementById("range-resolved");
const rangeResolvedOut = document.getElementById("range-resolved-out");
const showRangeResolved = () => {
document.getElementById("range-resolved-value").textContent = JSON.stringify(rangeResolved.value);
rangeResolvedOut.textContent = JSON.stringify(rangeResolved.absoluteValue);
};
rangeResolved.addEventListener("change", showRangeResolved);
customElements.whenDefined("et2-date-range")
.then(() => rangeResolved.updateComplete)
.then(() => {
rangeResolved.value = "Last year";
showRangeResolved();
});
</script>
Switching a saved range to fixed dates
Assigning a period name to a widget that is not relative resolves it once and fills the two date fields in, which is how a saved “last month” favourite becomes dates the user can then adjust.
Value: -
<et2-date-range id="range-converted" label="Last month, as dates"></et2-date-range>
<p>Value: <span id="range-converted-out">-</span></p>
<script>
const rangeConverted = document.getElementById("range-converted");
const rangeConvertedOut = document.getElementById("range-converted-out");
customElements.whenDefined("et2-date-range")
.then(() => rangeConverted.updateComplete)
.then(() => {rangeConverted.value = "Last month";})
.then(() => rangeConverted.fromElement.updateComplete)
.then(() => {rangeConvertedOut.textContent = JSON.stringify(rangeConverted.value);});
</script>
Properties
| Name | Description | Reflects | Type | Default |
|---|---|---|---|---|
relative
|
Is the date range relative (this week) or absolute (2016–02–15 – 2016–02–21). This will affect the value returned. |
boolean
|
- | |
value
|
An object with keys ‘from’ and ‘to’ for absolute ranges, or a relative range string |
{to:string,from:string}|string
|
- |
Learn more about attributes and properties.
Inherited properties (22)
Et2Widget
| Name | Description |
|---|---|
accesskey |
Accesskey provides a hint for generating a keyboard shortcut for the current element. The attribute value must consist of a single printable character. |
actions |
Set Actions on the widget Each action is defined as an object: move: { type: “drop”, acceptedTypes: “mail”, icon: “move”, caption: “Move to” onExecute: javascript:mail_move” } This will turn the widget into a drop target for “mail” drag types. When “mail” drag types are dropped, the global function mail_move(egwAction action, egwActionObject sender) will be called. The ID of the dragged “mail” will be in sender.id, some information about the sender will be in sender.context. The etemplate2 widget involved can typically be found in action.parent.data.widget, so your handler can operate in the widget context easily. The location varies depending on your action though. It might be action.parent.parent.data.widget To customise how the actions are handled for a particular widget, override _link_actions(). It handles the more widget-specific parts. |
align |
Used by Et2Box to determine alignment. Allowed values are left, right |
class |
CSS Class. This class is applied to the outside, on the web component itself. Due to how WebComponents work, this might not change anything inside the component. |
data |
Set the dataset from a CSV |
deferredProperties |
Any attribute that refers to row content cannot be resolved immediately, but some like booleans cannot stay a string because it’s a boolean attribute. We store them for later, and parse when they’re fully in their row. If you are creating a widget that can go in a nextmatch row, and it has boolean attributes that can change for each row, add those attributes into deferredProperties |
disabled |
Defines whether this widget is visibly disabled. The widget is still visible, but clearly cannot be interacted with. Widgets disabled in the template will not return a value to the application code, even if re-enabled via javascript before submitting. To allow a disabled widget to be re-enabled and return a value, disable via javascript in the app’s et2_ready() instead of an attribute in the template file. |
dom_id |
Get the actual DOM ID, which has been prefixed to make sure it’s unique. |
hidden |
The widget is not visible. As far as the user is concerned, the widget does not exist. Widgets hidden with an attribute in the template may not be created in the DOM, and will not return a value. Widgets can be hidden after creation, and they may return a value if hidden this way. |
id |
Get the ID of the widget |
label |
The label of the widget Legacy support for labels with %s that get wrapped around the widget Not the best way go with webComponents - shouldn’t modify their DOM like this |
noLang |
Disable any translations for the widget |
parentId |
Parent is different than what is specified in the template / hierarchy. Widget ID of another node to insert this node into instead of the normal location |
statustext |
Tooltip which is shown for this element on hover |
styles |
WebComponent * |
options |
Get property-values as object |
supportedWidgetClasses |
et2_widget compatability |
Et2InputWidget
| Name | Description |
|---|---|
autofocus |
Have browser focus this input on load. Overrides etemplate2.focusOnFirstInput(), use only once per page https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attributes |
hasFeedbackFor |
Get a list of feedback types |
translate |
List of properties that get translated Done separately to not interfere with properties - if we re-define label property, labels go missing. |
needed |
Compatibility for deprecated name “needed” |
LitElement
| Name | Description |
|---|---|
updateComplete |
A read-only promise that resolves when the component has finished updating. |
Events
| Name | Description | Event Detail |
|---|---|---|
change |
Missing description |
Event
|
Learn more about events.
Methods
| Name | Description | Arguments |
|---|---|---|
relativeToAbsolute()
|
Resolve a relative range name (“Last month”) into the two dates it covers Each entry’s from() is handed a copy of the reference day, and its to() is handed a copy of the from date that was just computed - the end of a range is expressed as an offset from its own start (“six days later”, “the end of that month”), never from today. Both get their own copy because the functions mutate what they are given. |
date: string, today: Date
|
Learn more about methods.
Inherited methods (29)
Et2Widget
| Name | Description |
|---|---|
checkCreateNamespace() |
Checks whether a namespace exists for this element in the content array. If yes, an own perspective of the content array is created. If not, the parent content manager is used. Constructor attributes are passed in case a child needs to make decisions |
clone() |
Creates a copy of this widget. |
createElementFromNode() |
Create a et2_widget from an XML node. First the type and attributes are read from the node. Then the readonly & modifications arrays are checked for changes specific to the loaded data. Then the appropriate constructor is called. After the constructor returns, the widget has a chance to further initialize itself from the XML node when the widget’s loadFromXML() method is called with the node. |
getArrayMgr() |
Returns the array manager object for the given part |
getArrayMgrs() |
Returns an associative array containing the top-most array managers. |
getChildren() |
Get child widgets Use |
getInstanceManager() |
Returns the instance manager |
getPath() |
Returns the path into the data array. By default, array manager takes care of this, but some extensions need to override this |
getRoot() |
Returns the base widget Usually this is the same as getInstanceManager().widgetContainer |
loadFromXML() |
Loads the widget tree from an XML node |
loadingFinished() |
Needed for legacy compatability. |
parseXMLAttrs() |
The parseXMLAttrs function takes an XML DOM attributes object and adds the given attributes to the _target associative array. This function also parses the legacyOptions. N.B. This is only used for legacy widgets. WebComponents use transformAttributes() and do their own handling of attributes. |
set_label() |
NOT the setter, since we cannot add to the DOM before connectedCallback() TODO: This is not best practice. Should just set property, DOM modification should be done in render https://lit-element.polymer-project.org/guide/templates#design-a-performant-template |
setArrayMgr() |
Sets the array manager for the given part |
setArrayMgrs() |
Sets all array manager objects - this function can be used to set the root array managers of the container object. |
setInstanceManager() |
Set the instance manager Normally this is not needed as it’s set on the top-level container, and we just return that reference |
_handleClick() |
Click handler calling custom handler set via onclick attribute to this.onclick |
destroy() |
et2_widget compatability |
set_class() |
Set the widget class |
set_disabled() |
Wrapper on this.disabled because legacy had it. |
set_statustext() |
supports legacy set_statustext |
Et2InputWidget
| Name | Description |
|---|---|
et2HandleBlur() |
If the value is unchanged, put any held validation messages back Named et2HandleBlur to avoid overwriting handleBlur() in Shoelace components |
et2HandleFocus() |
When input receives focus, clear any validation errors. If the value is the same on blur, we’ll put them back The ones from the server (ManualMessage) can interfere with submitting. Named et2HandleFocus to avoid overwriting handleFocus() in Shoelace components |
getInputNode() |
Get input to e.g. set aria-attributes |
handleSlChange() |
Handle sl-change event from Shoelace components and dispatch a change event so anything listening for change events can react to it instead of having to listen for both sl-change and change. |
isValid() |
Used by etemplate2 to determine if we can submit or not |
submit() |
Called whenever the template gets submitted. We return false if the widget is not valid, which cancels the submission. |
validate() |
Massively simplified validate, as compared to what ValidatorMixin gives us, since ValidatorMixin extends FormControlMixin which breaks SlSelect’s render() We take all validators for the widget, and if there’s a value (or field is required) we check the value with each validator. For array values we check each element with each validator. If the value does not pass the validator, we collect the message and display feedback to the user. We handle validation errors from the server with ManualMessages, which always “fail”. If the value is empty, we only validate if the field is required. |
_oldChange() |
Change handler calling custom handler set via onchange attribute |
Related
These widgets are related by naming but not by inheritance or sub-widget composition.