component-library

hi.
in "react semantic ui" document
search placeholder API is not documented while is implemented for component
please add
tnx

I hope that all component reference docs indicates the name of component for referencing at the header, just like Vant:

Thanks a lot.

<Select /> and <DatePicker /> don't offer the option of accessing name, id and other props once the onChange handler triggers. An event object with this information is accessible in the onChange handler for <Input />.

Feature description

Provide access to these variables for Select and DatePicker. It is needed when the component is being passed handler functions from an

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

Bug type

Component

Component name

MudDialog

What happened?

I need to be able set the Class property of an inline dialog to provide styling rules for the contained components. A uniquely named root class would enable this, but when set, it's excluded from render.

![image](https://user-images.githubusercontent.com/2884619/138448433-608cbac3-7267-4329-bfa8-6dcc8574fc1

Which @taiga-ui/* package(s) are relevant/releated to the feature request?

core

Description

New attribute tuiHighlightColor to control the color of the Highlight.
Discussed #919

(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