Skip to content

Conversation

@ttaylor-stack
Copy link
Collaborator

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Oct 17, 2025

⚠️ No Changeset found

Latest commit: f2bafc7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify
Copy link

netlify bot commented Oct 17, 2025

Deploy Preview for stacks ready!

Name Link
🔨 Latest commit f2bafc7
🔍 Latest deploy log https://app.netlify.com/projects/stacks/deploys/6900e9f0d8dead000838ace9
😎 Deploy Preview https://deploy-preview-2008--stacks.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Oct 17, 2025

Deploy Preview for stacks-svelte ready!

Name Link
🔨 Latest commit f2bafc7
🔍 Latest deploy log https://app.netlify.com/projects/stacks-svelte/deploys/6900e9f0c3884500088395b5
😎 Deploy Preview https://deploy-preview-2008--stacks-svelte.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@ttaylor-stack ttaylor-stack changed the base branch from develop to beta October 17, 2025 15:33
Copy link
Contributor

@dancormier dancormier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ttaylor-stack I looked it over and made a few broad suggestions that might help out. I'm happy to discuss more while we pair on Monday. Thanks for taking on this beastly redesign 🙂

transition: opacity 200ms var(--te-smooth); // Animate the transition to .is-loading

&:not(:last-child) {
margin-right: var(--_bu-icon-gap, 8px);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for the fallback 8px value here. Since --_bu-icon-gap is defined in a broader scope, it should always have a value.

}

&:not(:first-child) {
margin-left: var(--_bu-icon-gap, 8px);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. No need for the fallback 8px value.

--_bu-bc: transparent;
// --_bu-bg: inherit; // [1]
--_bu-br: var(--br-md);
--_bu-br: 20px;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using a hardcoded value here, I suggest using a border radius variable (I think --br-pill would be best).

Extra context: Design plans on simplifying our border radii to something like none (0), round (10px I think), pill (1000px), and potentially circle (100%).

I suggest adding a todo here to convert this value to an atomic value once border radius is updated in our libraries (see SPARK-91).

Comment on lines 9 to 11
--_bu-p: 10px;
--_bu-px: 16px;
--_bu-py: 10px;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When reasonably possible, I'd like to stick to sizing variables instead of hardcoded values. For example, 10px would be represented using a calc(var(--su8) + var(--su2)).

Extra context: We have sizing units that are variable and static. Check out this ADR for more info about this approach.

Comment on lines 224 to 230
--_bu-p: 0.6em;
--_bu-fs: 12px; // Override size-styles for custom font size
--_bu-px: 12px; // 12px padding as per Figma specs
--_bu-py: 10px;
--_bu-icon-gap: 4px; // 4px spacing as per Figma specs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sort of stuff will be tricky until we have base styles updates like typography figured out. You'll see a .size-styles mixin a couple of lines up. This mixin allows us apply the same styles for a given size across multiple components. We could modify that mixin to account for that but I'm leaning towards just adding a few todos to port things over to that mixin.

Comment on lines 235 to 238
--_bu-fs: 13px; // Override size-styles for custom font size
--_bu-px: 12px; // 12px padding as per Figma specs
--_bu-py: 10px; // Calculated to achieve 32px height: (32 - 12) / 2 = 10px
--_bu-icon-gap: 6px; // 6px spacing as per Figma specs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to achieve the desired button height with the suggested padding, we'll probably need to adjust line-height pretty significantly. For instance, the xs button can hit ~28px height with line-height: .5, but this is a very tight line height that would result in some rough display if it ever needs to wrap.

Example images

line-height: .5 single line

image

line-height: .5 multi-line

image

For the button sizes in general, I suggest asking via a comment on the Figma asking if the overall height is the goal over specific padding values. I suspect hitting ~28px height is more important. If that's true, I'd ignore the recommended padding values in favor of hitting the height while ensuring the text is vertically centered.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore padding specified in Figma and target height OR do recommendation above

display: inline-block;
font-family: inherit;
font-weight: normal;
font-weight: var(--_bu-fw, 600);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for the fallback value here

@CGuindon
Copy link
Collaborator

Discussion in this slack thread

  • It's missing the Tonal button (replacing Muted I think?)
  • I updated the Facbook icon a month ago and I probably broke something in this Facebook button (extra color class in there maybe?). Can we fix this as part of the new buttons? (nobody has noticed yet — I don't think we use this button in a lot of places)
Screenshot 2025-10-24 at 12 14 04 PM

--_bu-dropdown-bw: calc(var(--su-static4) - var(--su-static1));
--_bu-p: 0.6em;
--_bu-p: var(--su12);
--_bu-py: 6.285px; // Adjust to reach 28px height
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

round 6.285 down or up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants