* ProgressBar status feature added
* ProgressBar: Removed the css variables and use carbon-css instead.
The way of assigning the ProgressBar value has change. It is now a style
variable and scale-x is calculated in the css. This way prevent the
override of carbon css.
* Removed an unessacery span.
* Removed an unnecessary span.
* Added the status for the ProgressBarUx
* Remove `style css` and update docs.
* - Fixed the `capped` variable for more readability
- Updated docs `label` and `helperText`
- Updated docs and css
* fix: finished/error states cannot be indeterminate
* Run "yarn build:css"
* Re-run "yarn build:docs"
* test(progress-bar): assert `status` prop
* chore: add aria-busy and set valuenow to 0 when not active
---------
Co-authored-by: Eric Liu <ericyl.us@gmail.com>
Co-authored-by: Enrico Sacchetti <enrico@theetrain.ca>
The `bx--slider` class in the `Slider` component has max-width of `40rem`. Because `$$restProps` is spread to the top-level `div` element in `Slider`, the only way to override the style is to do so globally:
```css
:global(.bx--slider-container) {
width: 100%;
}
:global(.bx--slider) {
max-width: none;
}
```
This adds a `fullWidth` prop that sets a full width style using inline style attributes.
* feat(select): support number type
* Run "yarn build:docs"
* refactor(pagination): do not coerce `pageSize`, `page` to be numbers
* test(select): assert selected prop number type
* refactor(data-table): pass down sortable props instead of using context
* feat(data-table): support programmatic sorting
* test(data-table): assert new props
* docs(data-table): add "Programmatic sorting" example
* refactor(data-table): remove unused tableSortable store
* refactor(data-table): remove unused indices
* fix(combo-box): ListBoxField and ListBoxSelection have different `translateWithId` props
* fix(multi-select): ListBoxField and ListBoxSelection have different `translateWithId` props
* Run "yarn build docs"
* test: assert translateWithIdMenu, translateWIthIdInput props
* chore: update ignore rules, remove unused files
* refactor(icons): use icons from carbon-icons-svelte@11
* docs(time-picker): fix default value
* chore: upgrade carbon-icons-svelte to v11
* docs: update examples to use icons from carbon-icons-svelte@11
* docs: update number of icons [ci skip]
* docs: remove .bx--content override
* docs(ui-shell): add note on UI Shell theming
* docs(grid): touch up grid examples
* docs(theme): wrap localStorage in try catch
So that the site still works in Safari with all cookies blocked.
* docs: use prefixed all.css
Without vendor prefixes, some styles are lost in Safari.
* docs: remove svelte-preprocess from svelte.config.js
The `clearFiles` prop description currently reads "Override the default behavior of clearing the array of uploaded files."
This is misleading as `clearFiles` is a component accessor, not a `let` prop.
The non-filterable `MultiSelect` is missing a `blur` event.
Implementation-wise, we have to dispatch it and include the event as the `detail`. Otherwise, the filterable variant will dispatch "blur" twice because it has both a button and input.
The filterable `MultiSelect` continues to forward the blur event to the input.
Use the native `bind:value` to fix two-way reactivity. As a result, "type" is read through `$$restProps` because it cannot be dynamic when using `bind:value`.
Extend value type to include `null` for the "number" type. This is similar to how `NumberInput` works; `null` represents "no value."