Closed chenxi-20 closed 2 weeks ago
The changes in this pull request focus on updating the styling of the tabs component within the index.less
file. Key modifications include the use of CSS variables for the close icon dimensions, adjustments to margin properties, and refined visibility conditions for item separators. Additionally, hover and active states have been enhanced to align with updated design specifications, improving responsiveness across different tab orientations. Overall, these changes aim to enhance the visual consistency and user experience of the tabs component.
File Path | Change Summary |
---|---|
packages/theme/src/tabs/index.less | Updated close icon dimensions to use CSS variables, adjusted margin properties, refined item separator visibility, enhanced hover and active states, and added new CSS rules for different tab orientations. |
index.less
file for the tabs component.π In the land of tabs, where styles do play,
The close icon dances, in a flexible way.
With margins adjusted, and separators refined,
A user experience, beautifully aligned.
So hop with delight, for changes are here,
In the world of CSS, letβs give a cheer! π
packages/theme/src/tabs/index.less (4)
`258-259`: **LGTM! Using CSS variables for icon dimensions.** The change to use CSS variables for close icon dimensions improves maintainability and consistency. --- `591-596`: **Verify if the large right margin is necessary.** While the negative left margin (-20px) helps fix the floating issue, the large right margin (24px) seems excessive. Could you confirm if this large spacing is intentional and matches the design specifications? Consider if a smaller margin would suffice while maintaining proper spacing. --- `597-600`: **LGTM! Improved separator positioning.** The 1px left offset for the separator improves alignment within the button-card style. --- `1233-1234`: **LGTM! Logical separator visibility rules.** Good improvement to hide separators for the last child and active items, which enhances visual clarity.
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit