-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(tabs, tab-nav, tab-title, tab): add component tokens #10532
base: dev
Are you sure you want to change the base?
Conversation
:host .class-selectors :host([prop]) selectors @includes @Keyframes
simplify background color and border across appearance and kind
…openPR/7180-button # Conflicts: # packages/calcite-components/src/components/button/button.e2e.ts
* icon-color * icon-start-color * icon-end-color * x-button * drop unused anchor rule * border
@@ -46,36 +50,6 @@ | |||
<div class="child">large</div> | |||
</div> | |||
|
|||
<!-- simple tab-nav --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed since this is not a supported configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good Franco. Given our in-person conversation, I think most of the -hover -press tokens can be removed as these are slotted components. Also can the x-button be pulled into a function/mixin for reusability as well as the "accent-color" styles which I think should be shared across the app but I'd defer to @SkyeSeitz and @ashetland for that.
I was having a hard time explaining the change requests in comments so I made a draft PR #10579
@@ -19,7 +19,7 @@ | |||
.content { | |||
@apply text-n2h py-1; | |||
} | |||
.close-button { | |||
.x-button { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should these x-button
styles be moved to a shared mixin?
@@ -3,7 +3,7 @@ | |||
* | |||
* These properties can be overridden using the component's tag as selector. | |||
* | |||
* @prop --calcite-tab-content-block-padding: Specifies the block padding of the component's content in the `default` slot. | |||
* @prop --calcite-tab-content-block-padding: [Deprecated] Use `--calcite-tab-content-space-y` instead. Specifies the block padding of the component's content in the `default` slot. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know it's documented in "tabs" but I think we should add --calcite-tab-content-space-y
docs here as well since it's used in the component.
@@ -3,7 +3,7 @@ | |||
* | |||
* These properties can be overridden using the component's tag as selector. | |||
* | |||
* @prop --calcite-tab-content-block-padding: Specifies the block padding of the component's content in the `default` slot. | |||
* @prop --calcite-tab-content-block-padding: [Deprecated] Use `--calcite-tab-content-space-y` instead. Specifies the block padding of the component's content in the `default` slot. | |||
*/ | |||
|
|||
:host([selected]) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you replace lines 9 - 24 with the following to clean up styles
:host {
@apply hidden h-full w-full;
}
:host([selected]) {
@apply block h-full w-full overflow-auto;
section,
.container {
@apply block;
}
}
This PR has been automatically marked as stale because it has not had recent activity. Please close your PR if it is no longer relevant. Thank you for your contributions. |
Related Issue: #7180, #10497
Summary
Adds the following component tokens (CSS props):
Deprecates the following CSS props:
--calcite-tab-content-block-padding
Notes
XButton
to match close button styles and possibly consolidate in a follow-up PR.themed
test input tokens use internal ones defined and shared by the parenttabs
(Allowthemed
to specify token target for inherited, internal CSS props #10569 should help clean this up).