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.

Issue

While the Textarea component respects the resize prop for disabling or restricting resize capabilities, the TextareaField component doesn't seem to properly pass it through to the underlying Textarea

Reproduction
See this codesandbox for a working

<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

Feature request type

Enhance component

Component name

MudTable - PagerContent

Is your feature request related to a problem?

At the moment, there is no way to determine, where the Pager ist showing within the table.

Describe the solution you'd like

It would be great to have an option to specify the location of the pager (ie. at the top of the table, at the bottom or even both

(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