design-system

The ability to view Storybook stories with different themes was added in grommet/grommet#5674.

We need to make adjustments to the stories component by component to take advantage of the theming ability. The Button stories are currently using this enhancement and can be viewed on storybook. While

Which Component Need Enhancement 期望新增功能的组件

• Progress

What does the proposed API look like 期望支持的API

stroke属性支持渐变色

Feature Description 功能描述

Progress支持线性渐变颜色

Additional information 补充说明

目前type="line"，stroke传入到background-color属性，然而该属性并不支持渐变色。

The DatePicker component is already created and it's functional, but it was written some time ago and it can be refactored (migrating from class-based to hooks). In order to achieve a good result, we also need a good test coverage.

Running storyb

Issue summary

When rendering a list page in the web admin using Filters and promoted filters, the UI 'jumps' after re-hydration.

<img width="1425" alt="Screen Shot 2020-04-28 at 9 32 13 AM" src="https://user-images.gi

Is your feature request related to a problem? Please describe.
I don't think Theme UI should be opinionated on which SVGs should be used for the Radio & CheckBox components

Describe the solution you'd like
Probably an additional prop called customIcon maybe... based on which we could conditionally render the passed SVG icon otherwise we use the default icons?

**Describe alter

Component

DatePicker2

Reproduction link

Steps to reproduce

希望datepicker2的底层依赖dayjs，可以替换成其他的，比如moment，请参考Code Pen

Describe the bug
Previously opened column field tooltip value is not removed automatically when click other field tooltip value instead it remain their.

Build Details

Version : v8.1.0-BC4
Commit : 015578b81c26a5843747ba53b2fd92d40f0453cb
Build : 50428

Browser Details
This issue is occurring on all browsers.

Preconditions

1. Kibaana v8.1.0-BC3 must be availa

(moved over from https://github.com/github/design-systems/issues/860, thanks @smockle 👋 !)

Problem

Occasionally it’s useful to add an interactive element with the semantics of button (correctly represented in the AT)—but without its visual styles.

Solution

Other teams at GitHub spread the following object in sx props to destyle Buttons:

// Removes most of 'button'’s visual appearanc