Skip to content

Releases: adobe/spectrum-css

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Change Log

7.0.0

Patch Changes

6.1.0

Minor Changes

New feature

Minified and gzipped outputs available for all compiled CSS assets.

Patch Changes

Dependency alignment across the project.

6.0.1

Patch Changes

  • #3534 68e0057 Thanks @castastrophe! - Fixes a bug in the content of the dist/index-theme.css file.

    Expected index-theme.css to include the component selectors with component-level custom properties mapped to the --system prefixed ones in order to allow a component to support various contexts.

    Expected output example for the index-theme.css:

    .spectrum-ActionButton {
     --spectrum-actionbutton-background-color-default: var(--system-action-button-background-color-default);
     --spectrum-actionbutton-background-color-hover: var(--system-action-button-background-color-hover);
    
  • Updated dependencies [68e0057]:

6.0.0

Major Changes

  • #2786 6c19fcf Thanks @pfulton! - ## Breaking change

    This major update creates a bridge between the Spectrum 1 (S1) and Spectrum 2 (S2) designs, dubbed "Spectrum 2 Foundations". These do NOT reflect a fully migrated S2 component. This approach allows consumers to swap the appearance of their components between S1, Express, and S2 by leveraging a "system" layer that remaps the necessary component-level tokens to the appropriate token dataset.

    For these components to appear S2, you must load the assets with the @spectrum-css/tokens at v16 or higher.

    For S1 or Express, load assets with the @spectrum-css/tokens at v14.x or v15.x.

    If you are looking to implement a fully S2 design, please explore the next tag releases instead of using this foundations release. This release is used in Spectrum Web Components 1.x.

    Deprecations

    The metadata folder containing the mods.md and metadata.json assets has been removed from source. To find information about the components including what selectors, modifiers, and passthroughs are used, please see the dist/metadata.json asset shipped with every component containing CSS.

    The index-vars.css asset has been removed in this release as it was previously deprecated and is no longer maintained. Please use the index.css or index-base.css

    File usage

    If you are rendering components and need only the S2 Foundations styles, you can make use of the index.css asset which contains all the base styles plus the system mappings for S2 Foundations.

    If you are using this version to publish only an S1 or Express component, you can use the index-base.css plus the desired themes/(spectrum|express).css file.

    To render a component that can be easily swapped between the S2 Foundations, S1, or Express contexts, load index-base.css with the index-theme.css file and leverage the appropriate context classes (.spectrum--legacy for S1 and .spectrum--express for Express).

Patch Changes

5.3.1

Patch Changes

5.3.0

Minor Changes

  • #3502 562396e Thanks @castastrophe! - Simplify how the --system properties are mapped. By updating the logic in the postcss-add-theming-layer, we are now shipping cleaner, more readable --system property names. These custom properties are documented as NOT a part of the component API so although these result in a change to the custom property names, it does not impact the properties that are in the API and so do not constitute a breaking change. Expect to see no change to how component theming works or any visual regressions as a result of this change.

Patch Changes

5.2.0

Minor Changes

Patch Changes

5.1.4

Patch Changes

  • #3315 df7c4b1 Thanks @cdransf! - Resolves stylelint violation by removing undefined and unused token

5.1.3

Patch Changes

5.1.2

Patch Changes

5.1.1

Patch Changes

5.1.0

Minor Changes

Build optmizations to support minification

Output for all component CSS files is now being run through a lightweight optimizer (cssnano) which significantly reduces unnecessary whitespace. These changes reduce file size but should not have any ...

Read more

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Minor Changes

  • #3566 0fe73e9 Thanks @aramos-adobe! - # Popover overflow bug on Safari browser

    translateZ has been added to popover &.is-open. This is to prevent clipping of the filter: drop-shadow when overflow is applied on spectrum-Popover. This bug happens on the Safari browser. translateZ or translate3d on the &.is-open class accelerates the component to the GPU layer maintaining any transformations and animations.

    overflow: visible applied to CSS --withTip so the tip is still visible if overflow is applied to the component.

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes

@spectrum-css/[email protected]

20 Feb 18:41
db13d42
Compare
Choose a tag to compare

Patch Changes