component-library

Steps

Add a checkbox inside a dropdown, either as header or item.

Expected Result

• onClick fires

Actual Result

• onClick doesn't fire
• also note the weird font

Version

0.74.1

Testcase

https://codepen.io/anon/pen/zENBPx

<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

Discussed in nextui-org/nextui#269

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

MudTable

What happened?

When using a NoRecordsContent inside a MudTable with Striped and Hover enabled it is rendered using these classes also. However the content should be agnostic to them since they are used solely for rows.

Expected behavior

NoRecordsContent should render without Striped or Hover styles applied.

Reprod

(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