-
Notifications
You must be signed in to change notification settings - Fork 79
Closed
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.bugBug reports for broken functionality. Issues should include a reproduction of the bug.Bug reports for broken functionality. Issues should include a reproduction of the bug.calcite-componentsIssues specific to the @esri/calcite-components package.Issues specific to the @esri/calcite-components package.estimate - 1Very small fix or change (potentially a single line), doesn't require updates to tests.Very small fix or change (potentially a single line), doesn't 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 - highIssue should be addressed in the current milestone, impacts component or core functionalityIssue should be addressed in the current milestone, impacts component or core functionalityregressionIssues that are caused by changes in a release, but were working before that.Issues that are caused by changes in a release, but were working before that.
Milestone
Description
Check existing issues
- I have checked for existing issues to avoid duplicates
Actual Behavior
Looks like the top and bottom padding on header-content
was changed from 14px to 12px. This change was not intended for now so we need to revert that back.
Expected Behavior
The header content should retain the same 14px padding as before #9730
Reproduction Sample
https://codepen.io/driskull/pen/qBzrbwM
Reproduction Steps
- Open codepen
- Inspect header content then note 14px top and bottom padding
- change version to 2.11.0 and note the new 12px padding
Reproduction Version
2.11.0
Relevant Info
No response
Regression?
2.10.1
Priority impact
impact - p1 - need for current milestone
Impact
No response
Calcite package
- @esri/calcite-components
- @esri/calcite-components-angular
- @esri/calcite-components-react
- @esri/calcite-design-tokens
- @esri/eslint-plugin-calcite-components
Esri team
ArcGIS Maps SDK for JavaScript
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.bugBug reports for broken functionality. Issues should include a reproduction of the bug.Bug reports for broken functionality. Issues should include a reproduction of the bug.calcite-componentsIssues specific to the @esri/calcite-components package.Issues specific to the @esri/calcite-components package.estimate - 1Very small fix or change (potentially a single line), doesn't require updates to tests.Very small fix or change (potentially a single line), doesn't 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 - highIssue should be addressed in the current milestone, impacts component or core functionalityIssue should be addressed in the current milestone, impacts component or core functionalityregressionIssues that are caused by changes in a release, but were working before that.Issues that are caused by changes in a release, but were working before that.