·
79 commits
to develop
since this release
- NPM package: https://www.npmjs.com/package/@eccenca/gui-elements/v/26.1.0
- Storybook: https://62150dbccb2d77003a2a5093-lwzgjxztvq.chromatic.com/
Added
utilsuseComputedStyleFallbackoption forCssCustomProperties: if the CSSOM does not provide any property name for the used selector, e.g. because the declarations are part of a constructed and adopted stylesheet, then the names are read from the computed style of the matching element; disabled by default because the computed style also contains all inherited custom properties
Changed
<CodeEditor />shouldHaveMinimalSetup: even if set tofalse, the edit history feature is still enabled explicitly
<PropertyValuePair />- the two-column display is only used if the container is wide enough, this way property name columns do not get too small
- in narrower containers, property name and value are displayed as stacked rows
- make the breakpoint configurable via SCSS (
$eccgui-propertyvalue-size-column-breakpoint-small)
utils- values of CSS custom properties are resolved via the computed style of a matching element now, so they always represent what the browser really applies, e.g. references to other custom properties are already replaced
Fixed
<Tooltip />- inline
codemarkup was hardly readable because of low contrast
- inline
<PropertyName />- fix width if it contains a
<Label />with<OverflowText />children - the label tooltip is displayed correctly inside the container
- fix width if it contains a
<HandleDefault />- default handle class names were removed as soon as an
intentwas given - fix runtime error if the element holding the handle tools is not available
- default handle class names were removed as soon as an
utils- CSS custom properties are also found if their rule is nested inside a cascade layer (
@layer) or another grouping rule like@media,@supportsor@container; this affectstextToColorHash(),getEnabledColorsFromPalette(),getEnabledColorPropertiesFromPalette()andgetColorConfiguration() - CSS custom properties are also found if the given selector is only one part of the selector list of a rule, e.g.
:root, :host - stylesheets that are loaded from another origin do not break the collection of CSS custom properties anymore
- collecting CSS custom properties does not throw an error anymore in test environments where the style declaration of a CSS rule is not an iterable object, e.g. in jsdom
- empty results are not cached anymore, this way they are read again if the stylesheets are loaded later on
minimalColorDistanceis part of the cache key ofgetEnabledColorsFromPalette()andgetEnabledColorPropertiesFromPalette()now
- CSS custom properties are also found if their rule is nested inside a cascade layer (