-
Notifications
You must be signed in to change notification settings - Fork 79
Closed
Closed
Copy link
Labels
4 - verifiedIssues that have been tested, confirmed as mitigated, and are ready to close.Issues that have been tested, confirmed as mitigated, and are ready to close.ArcGIS Maps SDK for JavaScriptIssues logged by ArcGIS SDK for JavaScript team members.Issues logged by ArcGIS SDK for JavaScript team members.calcite-componentsIssues specific to the @esri/calcite-components package.Issues specific to the @esri/calcite-components package.designIssues that need design consultation prior to, or during, development.Issues that need design consultation prior to, or during, development.enhancementIssues tied to a new feature or request.Issues tied to a new feature or request.estimate - 2Small fix or update, may require updates to tests.Small fix or update, may require updates to tests.impact - p1 - need for current milestoneUser set priority impact status of p1 - need for current milestoneUser set priority impact status of p1 - need for current milestonep - mediumIssue is non core or affecting less that 60% of people using the libraryIssue is non core or affecting less that 60% of people using the library
Milestone
Description
Check existing issues
- I have checked for existing issues to avoid duplicates
Description
Both <calcite-input-date-picker>
and <calcite-input-time-picker>
support the readOnly
property, which has different styling than the disabled
property. This is a request for adding readOnly
property to <calcite-input-time-zone>
so we can keep styling consistent. We prefer readOnly
for accessibility reasons since disabled
prevents interaction with the component (and prevents things like copying the value by hand/keyboard).
Mixed "readOnly" and "disabled":
Acceptance Criteria
Support for readOnly
on <calcite-input-time-zone>
Relevant Info
No response
Which Component
<calcite-input-time-zone>
Example Use Case
Styles used by <calcite-input-date-picker>
and <calcite-input-time-picker>
Priority impact
p1 - need for current milestone
Calcite package
- @esri/calcite-components
- @esri/calcite-components-react
- @esri/eslint-plugin-calcite-components
Esri team
ArcGIS Maps SDK for JavaScript
hgonzago, tristan-morrison, banuelosj and nCastle1
Metadata
Metadata
Assignees
Labels
4 - verifiedIssues that have been tested, confirmed as mitigated, and are ready to close.Issues that have been tested, confirmed as mitigated, and are ready to close.ArcGIS Maps SDK for JavaScriptIssues logged by ArcGIS SDK for JavaScript team members.Issues logged by ArcGIS SDK for JavaScript team members.calcite-componentsIssues specific to the @esri/calcite-components package.Issues specific to the @esri/calcite-components package.designIssues that need design consultation prior to, or during, development.Issues that need design consultation prior to, or during, development.enhancementIssues tied to a new feature or request.Issues tied to a new feature or request.estimate - 2Small fix or update, may require updates to tests.Small fix or update, may require updates to tests.impact - p1 - need for current milestoneUser set priority impact status of p1 - need for current milestoneUser set priority impact status of p1 - need for current milestonep - mediumIssue is non core or affecting less that 60% of people using the libraryIssue is non core or affecting less that 60% of people using the library