Version Packages - #111
Merged
Merged
Version Packages#111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@1001-digital/components@2.11.0
Minor Changes
9e30abdThanks @jwahdatehagh! - Draw every hairline withborderinstead of a box-shadow ringInputs, buttons, comboboxes, tags, switches, sliders, pin inputs and panel
headers outlined themselves with
box-shadow: 0 0 0 1px, while cards, popoversand dialogs used a real
border. Browsers snap border widths down to wholedevice pixels but leave box-shadow spread unsnapped, so on fractional-DPR
screens the shadow rings painted about twice as heavy as the borders next to
them. Everything now uses
border/border-color, so all outlines share oneweight.
Shadow rings overlapped each other where two outlined boxes met; borders do not,
so the places that relied on that now leave exactly one border per shared edge:
the tag dismiss button keeps only its divider,
FormItemprefix/suffix and theleading controls of a
FormInputGroupdrop the border their neighbour draws,and dialog, popover and toast headers draw only the separator below them.
Hovering a tag's dismiss button now highlights the tag's border, which is the
line that button no longer draws.
The
--border-shadow/--border-shadow-highlighttokens remain forlayout-neutral rings. The multi transaction flow marker tokens change from
shadows to colors:
--multi-transaction-flow-marker-shadow,--multi-transaction-flow-marker-active-shadowand--multi-transaction-flow-marker-error-shadoware replaced by--multi-transaction-flow-marker-border-color,--multi-transaction-flow-marker-active-border-colorand--multi-transaction-flow-marker-error-border-color.Patch Changes
9e30abdThanks @jwahdatehagh! - Centre the alert dismiss button and its iconThe button was pinned at
--spacer-smfrom the top of the alert, so its box sathalf the difference between the icon size and the line height above the heading
next to it. It now inherits the alert's line box and centres on the first line.
Its 1em icon also sat inside a fixed
--size-4box, leaving 1.5px a side. Onfractional DPR screens that straddles a device pixel — the browser snapped one
side to 1px and the other to 2px, painting the X up and to the left of centre.
The box is now exactly one icon, so there is no leftover space to split.
Updated dependencies [
9e30abd]:@1001-digital/components.evm@4.2.0
Minor Changes
9e30abdThanks @jwahdatehagh! - Draw every hairline withborderinstead of a box-shadow ringInputs, buttons, comboboxes, tags, switches, sliders, pin inputs and panel
headers outlined themselves with
box-shadow: 0 0 0 1px, while cards, popoversand dialogs used a real
border. Browsers snap border widths down to wholedevice pixels but leave box-shadow spread unsnapped, so on fractional-DPR
screens the shadow rings painted about twice as heavy as the borders next to
them. Everything now uses
border/border-color, so all outlines share oneweight.
Shadow rings overlapped each other where two outlined boxes met; borders do not,
so the places that relied on that now leave exactly one border per shared edge:
the tag dismiss button keeps only its divider,
FormItemprefix/suffix and theleading controls of a
FormInputGroupdrop the border their neighbour draws,and dialog, popover and toast headers draw only the separator below them.
Hovering a tag's dismiss button now highlights the tag's border, which is the
line that button no longer draws.
The
--border-shadow/--border-shadow-highlighttokens remain forlayout-neutral rings. The multi transaction flow marker tokens change from
shadows to colors:
--multi-transaction-flow-marker-shadow,--multi-transaction-flow-marker-active-shadowand--multi-transaction-flow-marker-error-shadoware replaced by--multi-transaction-flow-marker-border-color,--multi-transaction-flow-marker-active-border-colorand--multi-transaction-flow-marker-error-border-color.Patch Changes
9e30abd,9e30abd]:@1001-digital/styles@2.8.0
Minor Changes
9e30abdThanks @jwahdatehagh! - Draw every hairline withborderinstead of a box-shadow ringInputs, buttons, comboboxes, tags, switches, sliders, pin inputs and panel
headers outlined themselves with
box-shadow: 0 0 0 1px, while cards, popoversand dialogs used a real
border. Browsers snap border widths down to wholedevice pixels but leave box-shadow spread unsnapped, so on fractional-DPR
screens the shadow rings painted about twice as heavy as the borders next to
them. Everything now uses
border/border-color, so all outlines share oneweight.
Shadow rings overlapped each other where two outlined boxes met; borders do not,
so the places that relied on that now leave exactly one border per shared edge:
the tag dismiss button keeps only its divider,
FormItemprefix/suffix and theleading controls of a
FormInputGroupdrop the border their neighbour draws,and dialog, popover and toast headers draw only the separator below them.
Hovering a tag's dismiss button now highlights the tag's border, which is the
line that button no longer draws.
The
--border-shadow/--border-shadow-highlighttokens remain forlayout-neutral rings. The multi transaction flow marker tokens change from
shadows to colors:
--multi-transaction-flow-marker-shadow,--multi-transaction-flow-marker-active-shadowand--multi-transaction-flow-marker-error-shadoware replaced by--multi-transaction-flow-marker-border-color,--multi-transaction-flow-marker-active-border-colorand--multi-transaction-flow-marker-error-border-color.@1001-digital/layers.base@2.1.10
Patch Changes
9e30abd,9e30abd]:@1001-digital/layers.evm@4.0.2
Patch Changes
9e30abd,9e30abd]: