input-time-zone
with empty string not defaulting to local time zone
#9292
Labels
0 - new
New issues that need assignment.
ArcGIS Field Apps
Issues logged by ArcGIS Field Apps team members.
bug
Bug reports for broken functionality. Issues should include a reproduction of the bug.
calcite-components
Issues specific to the @esri/calcite-components package.
estimate - 2
Small fix or update, may require updates to tests.
impact - p3 - not time sensitive
User set priority impact status of p3 - not time sensitive
needs milestone
Planning workflow - pending milestone assignment, has priority and/or estimate.
p - medium
Issue is non core or affecting less that 60% of people using the library
Check existing issues
Actual Behavior
Given an
input-time-zone
with a value ofundefined
, the user's local time zone is automatically selected. However, given aninput-time-zone
with an empty string value, the UTC time zone is automatically selected.Expected Behavior
Given a non-clearable
input-time-zone
with an empty string value, the user's local time zone is automatically selected.Reproduction Sample
https://codepen.io/nwhittaker-esri/pen/ZENEKJe
Reproduction Steps
input-time-zone
elementsinput-time-zone
labeled "Empty string value" should match the value of theinput-time-zone
labeled "Undefined value"Reproduction Version
2.8.0
Relevant Info
Per the doc page ☝️. I suppose this issue is assuming an empty string counts as "no value".
Regression?
No response
Priority impact
p4 - not time sensitive
Impact
Represents some added debugging time and code complexity to the consumer to normalize the "empty" value that's passed into the
input-time-zone
.Calcite package
Esri team
ArcGIS Field Apps
The text was updated successfully, but these errors were encountered: