repo stringclasses 21
values | pull_number float64 45 194k | instance_id stringlengths 16 34 | issue_numbers stringlengths 6 27 | base_commit stringlengths 40 40 | patch stringlengths 263 270k | test_patch stringlengths 312 408k | problem_statement stringlengths 38 47.6k | hints_text stringlengths 1 257k ⌀ | created_at stringdate 2016-01-11 17:37:29 2024-10-18 14:52:41 | language stringclasses 4
values | Dockerfile stringclasses 279
values | P2P stringlengths 2 10.2M | F2P stringlengths 11 38.9k | F2F stringclasses 86
values | test_command stringlengths 27 11.4k | task_category stringclasses 5
values | is_no_nodes bool 2
classes | is_func_only bool 2
classes | is_class_only bool 2
classes | is_mixed bool 2
classes | num_func_changes int64 0 238 | num_class_changes int64 0 70 | num_nodes int64 0 264 | is_single_func bool 2
classes | is_single_class bool 2
classes | modified_nodes stringlengths 2 42.2k |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
mui/material-ui | 33,777 | mui__material-ui-33777 | ['33771'] | 812876d87be3ceeed0122b60e7003518b8ac6ea2 | diff --git a/docs/data/material/customization/density/DensityTool.js b/docs/data/material/customization/density/DensityTool.js
--- a/docs/data/material/customization/density/DensityTool.js
+++ b/docs/data/material/customization/density/DensityTool.js
@@ -25,9 +25,20 @@ export default function DensityTool() {
};
... | diff --git a/packages/mui-material/src/Grid/Grid.test.js b/packages/mui-material/src/Grid/Grid.test.js
--- a/packages/mui-material/src/Grid/Grid.test.js
+++ b/packages/mui-material/src/Grid/Grid.test.js
@@ -689,6 +689,25 @@ describe('Material UI <Grid />', () => {
'Warning: Failed prop type: The prop `spacing`... | [docs] Demo DensityTool crashes
<!-- Please make sure you have fullfilled the following items before submitting -->
<!-- Checked checkbox should look like this: [x] -->
- [x] I have [searched for similar issues](https://github.com/mui/material-ui/issues?q=is%3Aissue%20%5Bdocs%5D%20Demo%20DensityTool%20crashes) in thi... | null | 2022-08-03 08:40:36+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Grid/Grid.test.js->Material UI <Grid /> prop: container should apply the correct number of columns for nested containers with undefined prop columns', 'packages/mui-material/src/Grid/Grid.test.js->Material UI <Grid /> prop: rowSpacing, columnSpacing should generate correct responsive styles ... | ['packages/mui-material/src/Grid/Grid.test.js->Material UI <Grid /> prop: spacing should not throw error for setting zero spacing in theme'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Grid/Grid.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["docs/data/material/customization/density/DensityTool.js->program->function_declaration:DensityTool", "packages/mui-material/src/Grid/Grid.js->program->function_declaration:generateRowGap", "packages/mui-material/src/Grid/Grid.js->program->function_declaration:generateColumnGap"] |
mui/material-ui | 33,797 | mui__material-ui-33797 | ['33231'] | 30484b8d93b8255a2617d7af134653f4d29bcd4b | diff --git a/docs/pages/material-ui/api/table-pagination.json b/docs/pages/material-ui/api/table-pagination.json
--- a/docs/pages/material-ui/api/table-pagination.json
+++ b/docs/pages/material-ui/api/table-pagination.json
@@ -60,7 +60,14 @@
"slotProps": {
"type": {
"name": "shape",
- "descr... | diff --git a/packages/mui-material/src/TablePagination/TablePagination.test.js b/packages/mui-material/src/TablePagination/TablePagination.test.js
--- a/packages/mui-material/src/TablePagination/TablePagination.test.js
+++ b/packages/mui-material/src/TablePagination/TablePagination.test.js
@@ -10,6 +10,12 @@ import Tab... | [TablePagination] Add ability to change icons used in TablePaginationActions
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
The First, Previous, Next, and Last icons are all hard-coded to be MUI icons. These should be conf... | Looks like we can add the `components` & `componentsProps` API here to allow people to override all slots available.
If this is a blocker you can create a custom `TablePaginationAction` component and adjust it to your needs.
Hey, @mnajdova,
I would like to work on this issue if no one else is working on it.
Thanks! | 2022-08-04 10:44:06+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: labelRowsPerPage labels the select for the current page', 'packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: showLastButton should change the page', 'packages/mui-material/src/TableP... | ['packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: slots should render custom action button icons', 'packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: slots should render custom action buttons', 'packages/mui-material/src/TablePagina... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/TablePagination/TablePagination.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,801 | mui__material-ui-33801 | ['33246'] | 2991f58b34601595e5907a597deacdf753ab35f1 | diff --git a/docs/pages/material-ui/api/chip.json b/docs/pages/material-ui/api/chip.json
--- a/docs/pages/material-ui/api/chip.json
+++ b/docs/pages/material-ui/api/chip.json
@@ -44,8 +44,12 @@
"root",
"sizeSmall",
"sizeMedium",
+ "colorError",
+ "colorInfo",
"colorPrimary",
... | diff --git a/packages/mui-material/src/Chip/Chip.test.js b/packages/mui-material/src/Chip/Chip.test.js
--- a/packages/mui-material/src/Chip/Chip.test.js
+++ b/packages/mui-material/src/Chip/Chip.test.js
@@ -58,18 +58,14 @@ describe('<Chip />', () => {
expect(chip).not.to.have.class(classes.deletableColorSecondar... | Mui Chip missing colorError in chipClasses.d.ts
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
tslint error when trying to `styleOverrides` on `colorError`, example
```
MuiChip: {
styleOverrides: {
c... | @totszwai we can add it 👍 Would you like to prepare a PR for it? Note that you can always use:
```
MuiChip: {
styleOverrides: {
root: ({ ownerState }) => {{
...(ownerState.color === 'error' && {
backgroundColor: "rebeccapurple",
})
}
}}
}
... | 2022-08-04 15:01:45+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Chip/Chip.test.js-><Chip /> prop: size should render the label with the labelSmall class', 'packages/mui-material/src/Chip/Chip.test.js-><Chip /> MUI component API prop: component can render another root component with the `component` prop', "packages/mui-material/src/Chip/Chip.test.js-><Chi... | ['packages/mui-material/src/Chip/Chip.test.js-><Chip /> text only should render with the color class name based on the color prop'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,812 | mui__material-ui-33812 | ['33232'] | e59262926c473fa1f6356f3ad150a9ca82e4ae0c | diff --git a/docs/pages/material-ui/api/breadcrumbs.json b/docs/pages/material-ui/api/breadcrumbs.json
--- a/docs/pages/material-ui/api/breadcrumbs.json
+++ b/docs/pages/material-ui/api/breadcrumbs.json
@@ -14,6 +14,14 @@
},
"maxItems": { "type": { "name": "custom", "description": "integer" }, "default": "8" ... | diff --git a/packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js b/packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js
--- a/packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js
+++ b/packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js
@@ -8,6 +8,7 @@ import {
strictModeDoubleLoggingSupressed,... | [Breadcrumbs] Add ability to change icon used in BreadcrumbCollapsed
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
The icon used for BreadcrumbCollapse is hard-coded to be the MUI MoreHorizon icon. This should be configur... | Looks like we can add the `components` & `componentsProps` API here to allow people to override all slots available.
Hey, @mnajdova,
I would like to work on this issue if no one else is working on it.
Thanks! | 2022-08-05 09:50:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js-><Breadcrumbs /> MUI component API prop: component can render another root component with the `component` prop', 'packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js-><Breadcrumbs /> should expand when `BreadcrumbCollapsed` is clicked', "packages/mui-mat... | ['packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js-><Breadcrumbs /> prop: slots and slotProps should show custom collapsed icon', 'packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js-><Breadcrumbs /> prop: slots and slotProps should apply slotProps to collapsed icon'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Breadcrumbs/Breadcrumbs.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-material/src/Breadcrumbs/BreadcrumbCollapsed.js->program->function_declaration:BreadcrumbCollapsed"] |
mui/material-ui | 33,820 | mui__material-ui-33820 | ['33615'] | 91ad7e8afe2b43b61815c31830f8b1a553fc9e91 | diff --git a/docs/pages/material-ui/api/icon-button.json b/docs/pages/material-ui/api/icon-button.json
--- a/docs/pages/material-ui/api/icon-button.json
+++ b/docs/pages/material-ui/api/icon-button.json
@@ -42,6 +42,10 @@
"colorInherit",
"colorPrimary",
"colorSecondary",
+ "colorError",
+ ... | diff --git a/packages/mui-material/src/IconButton/IconButton.test.js b/packages/mui-material/src/IconButton/IconButton.test.js
--- a/packages/mui-material/src/IconButton/IconButton.test.js
+++ b/packages/mui-material/src/IconButton/IconButton.test.js
@@ -4,6 +4,7 @@ import PropTypes from 'prop-types';
import { createR... | [IconButton] `iconButtonClasses` does not contain classes for `colorError`, `colorInfo`, etc.
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
The `color` prop on the `IconButton` component allows any of the `theme.palatte` c... | @lindapaiste Thanks for the detailed issue. Yes, some color properties are missing in `IconButtonClasses` type. Would you like to create a PR for it?
---
When you said looking at the props directly, I think you mean something along these lines with the styled API https://codesandbox.io/s/upbeat-heyrovsky-he993o. ... | 2022-08-06 13:33:08+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/IconButton/IconButton.test.js-><IconButton /> MUI component API should render without errors in ReactTestRenderer', 'packages/mui-material/src/IconButton/IconButton.test.js-><IconButton /> prop: disabled should disable the component', 'packages/mui-material/src/IconButton/IconButton.test.js-... | ['packages/mui-material/src/IconButton/IconButton.test.js-><IconButton /> prop: color should render the error class', 'packages/mui-material/src/IconButton/IconButton.test.js-><IconButton /> prop: color should render the warning class', 'packages/mui-material/src/IconButton/IconButton.test.js-><IconButton /> prop: colo... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/IconButton/IconButton.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,863 | mui__material-ui-33863 | ['33235'] | 9f7a2bfac55faed1b1c6c7b4b6d1b1659a076bab | diff --git a/docs/pages/material-ui/api/tab-scroll-button.json b/docs/pages/material-ui/api/tab-scroll-button.json
--- a/docs/pages/material-ui/api/tab-scroll-button.json
+++ b/docs/pages/material-ui/api/tab-scroll-button.json
@@ -11,6 +11,20 @@
"children": { "type": { "name": "node" } },
"classes": { "type":... | diff --git a/packages/mui-material/src/TabScrollButton/TabScrollButton.test.js b/packages/mui-material/src/TabScrollButton/TabScrollButton.test.js
--- a/packages/mui-material/src/TabScrollButton/TabScrollButton.test.js
+++ b/packages/mui-material/src/TabScrollButton/TabScrollButton.test.js
@@ -2,6 +2,8 @@ import * as R... | [TabScrollButton] Add ability to change left and right icons
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
The left and right icons are both hard-coded to be MUI icons. These should be configurable through props for MUI c... | You could use the `ScrollButtonComponent` prop to override the component while we have a better API for it. Adding a `components` & `componentsProps` to the Tabs component sounds great.
Is this open for contributing?
Yes @antariksh17
| 2022-08-08 17:37:02+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons should not hide scroll buttons when allowScrollButtonsMobile is true', 'packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> prop: children should accept a null child', 'packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> keyboard navigation... | ['packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> props: slots and slotProps, should render custom start and end icons', 'packages/mui-material/src/TabScrollButton/TabScrollButton.test.js-><TabScrollButton /> should render with the custom start icon', 'packages/mui-material/src/TabScrollButton/TabScrollButton.tes... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Tabs/Tabs.test.js packages/mui-material/src/TabScrollButton/TabScrollButton.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,873 | mui__material-ui-33873 | ['33060'] | 89c820ac86ca54d6d8b25309f9b43803e68903dc | diff --git a/packages/mui-base/src/InputUnstyled/InputUnstyled.tsx b/packages/mui-base/src/InputUnstyled/InputUnstyled.tsx
--- a/packages/mui-base/src/InputUnstyled/InputUnstyled.tsx
+++ b/packages/mui-base/src/InputUnstyled/InputUnstyled.tsx
@@ -42,8 +42,6 @@ const InputUnstyled = React.forwardRef(function InputUnstyl... | diff --git a/packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx b/packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx
--- a/packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx
+++ b/packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx
@@ -30,4 +30,36 @@ describe('<InputUnstyled />', () => {
... | [InputUnstyled] not forwarding textarea specific props (rows, maxRows, minRows)
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
`rows`, `minRows`, `maxRows` props have no effect when the `multiline` flag is set for... | null | 2022-08-09 13:51:03+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ["packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx-><InputUnstyled /> MUI unstyled component API sets custom properties on Input slot's element", 'packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx-><InputUnstyled /> MUI unstyled component API merges the class names provided in componentsProps.input w... | ['packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx-><InputUnstyled /> prop: multiline should pass the rows prop to the underlying textarea when multiline=true'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/InputUnstyled/InputUnstyled.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,880 | mui__material-ui-33880 | ['33255'] | 71a18fb6a9252e2200a0d576e66d55fbd81b85bd | diff --git a/packages/mui-material/src/ListItemText/ListItemText.js b/packages/mui-material/src/ListItemText/ListItemText.js
--- a/packages/mui-material/src/ListItemText/ListItemText.js
+++ b/packages/mui-material/src/ListItemText/ListItemText.js
@@ -84,7 +84,7 @@ const ListItemText = React.forwardRef(function ListItem... | diff --git a/packages/mui-material/src/ListItemText/ListItemText.test.js b/packages/mui-material/src/ListItemText/ListItemText.test.js
--- a/packages/mui-material/src/ListItemText/ListItemText.test.js
+++ b/packages/mui-material/src/ListItemText/ListItemText.test.js
@@ -155,6 +155,27 @@ describe('<ListItemText />', () ... | [ListItemText] primaryTypographyProps doesn't include variantMapping
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
While using ListItemText and providing a variant to `primaryTypographyProps ` it defaults to a span. And si... | Looks like a bug.
As a workaround, you can change the underlying element for a one-off situation like this with the `component` prop (Keeping the variant styles intact). Take a look at the [CodeSandbox](https://codesandbox.io/s/condescending-cache-pfo7h4?file=/src/App.tsx). The underlying element is changed to `h4` ... | 2022-08-10 08:58:57+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/ListItemText/ListItemText.test.js-><ListItemText /> should render with no children', 'packages/mui-material/src/ListItemText/ListItemText.test.js-><ListItemText /> should fall back to the default tag name if no variant provided', 'packages/mui-material/src/ListItemText/ListItemText.test.js->... | ['packages/mui-material/src/ListItemText/ListItemText.test.js-><ListItemText /> should use variant if provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/ListItemText/ListItemText.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,957 | mui__material-ui-33957 | ['33881'] | 8d6bae2e39b9c6e28caf49e0fb930ccfba4b711f | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.js b/packages/mui-material/src/Autocomplete/Autocomplete.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.js
@@ -592,7 +592,7 @@ const Autocomplete = React.forwardRef(function Autoco... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -2525,6 +2525,22 @@ describe('<Autocomplete />', (... | Autocomplete: keepMounted prop not working
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
When you pass `keepMounted` prop to Autocomplete it doesn't work:
`
componentsProps={{
popper: {
keepMoun... | Thanks for reporting. It's a bug. | 2022-08-17 05:09:13+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: componentsProps should keep AutocompletePopper mounted if keepMounted is true in popper props'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,974 | mui__material-ui-33974 | ['33894'] | df891841e991a4c5e84cd20b79352b18b04fba84 | diff --git a/packages/mui-material/src/Select/Select.js b/packages/mui-material/src/Select/Select.js
--- a/packages/mui-material/src/Select/Select.js
+++ b/packages/mui-material/src/Select/Select.js
@@ -114,7 +114,8 @@ const Select = React.forwardRef(function Select(inProps, ref) {
...(multiple && native && varian... | diff --git a/packages/mui-material/src/TablePagination/TablePagination.test.js b/packages/mui-material/src/TablePagination/TablePagination.test.js
--- a/packages/mui-material/src/TablePagination/TablePagination.test.js
+++ b/packages/mui-material/src/TablePagination/TablePagination.test.js
@@ -7,6 +7,9 @@ import TableF... | [TablePagination] select cannot be outlined
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
When adding `SelectProps={{ variant: "outlined" }}` to TablePagination not all needed classes are applied and root div gets variant=... | Thanks for the report! Looks like a bug. | 2022-08-18 09:57:00+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: labelRowsPerPage labels the select for the current page', 'packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: showLastButton should change the page', 'packages/mui-material/src/TableP... | ['packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> should not have "variant" attribute on TablePaginationSelect', 'packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: SelectProps should be able to apply the outlined variant to select', 'pack... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/TablePagination/TablePagination.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 33,994 | mui__material-ui-33994 | ['33993'] | 6ba3522921da7cd3bef8065954f62456e1b73fed | diff --git a/docs/pages/material-ui/api/avatar-group.json b/docs/pages/material-ui/api/avatar-group.json
--- a/docs/pages/material-ui/api/avatar-group.json
+++ b/docs/pages/material-ui/api/avatar-group.json
@@ -2,6 +2,7 @@
"props": {
"children": { "type": { "name": "node" } },
"classes": { "type": { "name"... | diff --git a/packages/mui-material/src/AvatarGroup/AvatarGroup.test.js b/packages/mui-material/src/AvatarGroup/AvatarGroup.test.js
--- a/packages/mui-material/src/AvatarGroup/AvatarGroup.test.js
+++ b/packages/mui-material/src/AvatarGroup/AvatarGroup.test.js
@@ -18,7 +18,7 @@ describe('<AvatarGroup />', () => {
... | AvatarGroup and Avatar use unstructured markup
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Currently, `AvatarGroup` and `Avatar` generate `<div>`s for markup, which is not semantic/structured.
```html
<div ... | null | 2022-08-19 16:17:02+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/AvatarGroup/AvatarGroup.test.js-><AvatarGroup /> should display 2 avatars and "+2"', 'packages/mui-material/src/AvatarGroup/AvatarGroup.test.js-><AvatarGroup /> should display all avatars with the specified variant', 'packages/mui-material/src/AvatarGroup/AvatarGroup.test.js-><AvatarGroup />... | ['packages/mui-material/src/AvatarGroup/AvatarGroup.test.js-><AvatarGroup /> MUI component API prop: component can render another root component with the `component` prop'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/AvatarGroup/AvatarGroup.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,138 | mui__material-ui-34138 | ['34137'] | 67073cc35a741e9f45aa0d54bc00918a9c05fdb4 | diff --git a/docs/pages/material-ui/api/step.json b/docs/pages/material-ui/api/step.json
--- a/docs/pages/material-ui/api/step.json
+++ b/docs/pages/material-ui/api/step.json
@@ -4,6 +4,7 @@
"children": { "type": { "name": "node" } },
"classes": { "type": { "name": "object" } },
"completed": { "type": { ... | diff --git a/packages/mui-material/src/Step/Step.test.js b/packages/mui-material/src/Step/Step.test.js
--- a/packages/mui-material/src/Step/Step.test.js
+++ b/packages/mui-material/src/Step/Step.test.js
@@ -16,7 +16,7 @@ describe('<Step />', () => {
muiName: 'MuiStep',
testVariantProps: { variant: 'foo' },
... | Stepper and Step use unstructured markup
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Currently, Stepper and Step generate <div>s for markup, which is not semantic/structured.
### Expected behavior 🤔
Using a list would... | null | 2022-08-30 20:20:01+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Stepper/Stepper.test.tsx-><Stepper /> step connector should pass completed prop to connector when second step is completed', 'packages/mui-material/src/Stepper/Stepper.test.tsx-><Stepper /> step connector should have a default step connector', 'packages/mui-material/src/Stepper/Stepper.test.... | ['packages/mui-material/src/Stepper/Stepper.test.tsx-><Stepper /> MUI component API prop: component can render another root component with the `component` prop', 'packages/mui-material/src/Step/Step.test.js-><Step /> MUI component API prop: component can render another root component with the `component` prop'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Stepper/Stepper.test.tsx packages/mui-material/src/Step/Step.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,158 | mui__material-ui-34158 | ['33901'] | d88ab9ebdc63157a7efcf582e65d4f6c58e5f576 | diff --git a/docs/data/base/components/select/UnstyledSelectControlled.js b/docs/data/base/components/select/UnstyledSelectControlled.js
--- a/docs/data/base/components/select/UnstyledSelectControlled.js
+++ b/docs/data/base/components/select/UnstyledSelectControlled.js
@@ -165,7 +165,7 @@ export default function Unsty... | diff --git a/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts b/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts
--- a/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts
+++ b/packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts
@@ -1,3 +1,4 @@
+impo... | [SelectUnstyled] Event is not passed to the onChange handler
The SelectUnstyled's (and MultiSelectUnstyled's) onChange handler is called with the selected value as the first parameter. This is not in line with other components (and native elements) that have an event associated with the change as the first parameter.
... | null | 2022-08-31 12:57:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/SelectUnstyled/SelectUnstyled.test.tsx->SelectUnstyled closes the listbox without selecting an option when focus is lost', 'packages/mui-base/src/ListboxUnstyled/defaultListboxReducer.test.ts->useListbox defaultReducer action: optionClick remove the clicked value from the selection if selectMult... | ['packages/mui-base/src/MultiSelectUnstyled/MultiSelectUnstyled.test.tsx->MultiSelectUnstyled sets a value correctly when interacted by a user and external code', 'packages/mui-base/src/MultiSelectUnstyled/MultiSelectUnstyled.test.tsx->MultiSelectUnstyled prop: onChange is called when the Select value changes', 'packag... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/ListboxUnstyled/useControllableReducer.test.tsx packages/mui-base/src/MultiSelectUnstyled/MultiSelectUnstyled.test.tsx packages/mui-base/src/SelectUnstyled/SelectUnstyled.test.tsx packages/mui-base/src/ListboxUnstyled/d... | Feature | false | true | false | false | 10 | 0 | 10 | false | false | ["docs/data/base/components/select/UnstyledSelectObjectValuesForm.js->program->function_declaration:UnstyledSelectObjectValues", "packages/mui-base/src/ListboxUnstyled/useControllableReducer.ts->program->function_declaration:useStateChangeDetection", "docs/data/base/components/select/UnstyledSelectObjectValues.js->prog... |
mui/material-ui | 34,159 | mui__material-ui-34159 | ['34028'] | 43a929dda5a0776bcc05f4624a5648441d44c7b2 | diff --git a/packages/mui-material/src/ListItemButton/ListItemButton.js b/packages/mui-material/src/ListItemButton/ListItemButton.js
--- a/packages/mui-material/src/ListItemButton/ListItemButton.js
+++ b/packages/mui-material/src/ListItemButton/ListItemButton.js
@@ -181,7 +181,8 @@ const ListItemButton = React.forwardR... | diff --git a/packages/mui-material/src/ListItemButton/ListItemButton.test.js b/packages/mui-material/src/ListItemButton/ListItemButton.test.js
--- a/packages/mui-material/src/ListItemButton/ListItemButton.test.js
+++ b/packages/mui-material/src/ListItemButton/ListItemButton.test.js
@@ -3,6 +3,7 @@ import { expect } fro... | LinkedComponent not respected by ListItemButton
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Supplying `LinkComponent` to `ListItemButton` does not cause its `component` to be overriden.
### Expected behavior 🤔
Supplyi... | extra context:
ListItemButton forces compoment to `a` if `href` is set
https://github.com/mui/material-ui/blob/dfc0b89c665de8e5e3e4ecf68d8c782e74dbb65c/packages/mui-material/src/ListItemButton/ListItemButton.js#L180
I believe the idea was that undelying `ButtonBase` will handle `LinkComponent`. But `ButtonBase... | 2022-08-31 15:50:19+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/ListItemButton/ListItemButton.test.js-><ListItemButton /> context: dense should forward the context', 'packages/mui-material/src/ListItemButton/ListItemButton.test.js-><ListItemButton /> prop: LinkComponent should ignore LinkComponent is component is provided', 'packages/mui-material/src/Lis... | ['packages/mui-material/src/ListItemButton/ListItemButton.test.js-><ListItemButton /> prop: LinkComponent should rendered as LinkComponent (from theme MuiButtonBase) when href is provided', 'packages/mui-material/src/ListItemButton/ListItemButton.test.js-><ListItemButton /> prop: LinkComponent should rendered as LinkCo... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/ListItemButton/ListItemButton.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,207 | mui__material-ui-34207 | ['34198'] | 1a4263a50af00eaffdca2e58b8ff16d62c4408a7 | diff --git a/docs/data/material/components/checkboxes/CheckboxLabels.js b/docs/data/material/components/checkboxes/CheckboxLabels.js
--- a/docs/data/material/components/checkboxes/CheckboxLabels.js
+++ b/docs/data/material/components/checkboxes/CheckboxLabels.js
@@ -7,6 +7,7 @@ export default function CheckboxLabels() ... | diff --git a/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js b/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js
--- a/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js
+++ b/packages/mui-material/src/FormControlLabel/FormControlLabel.test.js
@@ -179,6 +179,23 @@ ... | [FormControlLabel] Support `required`
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Implementing a labeled checkbox with a "required" asterisk, such as the following, is currently not possible without workarounds:
![ima... | null | 2022-09-06 17:04:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> with FormControl enabled should be overridden by props', 'packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> MUI component API merges the class names provided in slotsProps.typography with ... | ['packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> with FormControl required should be overridden by props', 'packages/mui-material/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: required should visually show an asterisk but not include it in the a11y ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/FormControlLabel/FormControlLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/data/material/components/switches/SwitchLabels.js->program->function_declaration:SwitchLabels", "docs/data/material/components/checkboxes/CheckboxLabels.js->program->function_declaration:CheckboxLabels"] |
mui/material-ui | 34,229 | mui__material-ui-34229 | ['32958'] | fa62bf35e109ede215cb8cbae66ba4d6a30fef60 | diff --git a/packages/mui-material/src/Select/SelectInput.js b/packages/mui-material/src/Select/SelectInput.js
--- a/packages/mui-material/src/Select/SelectInput.js
+++ b/packages/mui-material/src/Select/SelectInput.js
@@ -158,6 +158,8 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) {
}
... | diff --git a/packages/mui-material/src/Select/Select.test.js b/packages/mui-material/src/Select/Select.test.js
--- a/packages/mui-material/src/Select/Select.test.js
+++ b/packages/mui-material/src/Select/Select.test.js
@@ -851,27 +851,29 @@ describe('<Select />', () => {
});
describe('prop: autoWidth', () => {
... | Select's popover can be shorter than input because of adornments
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
... | Thanks for the report. Would you like to try working on a fix?
Spent an hour snooping around, managed to find where the Menu is rendered, still have no idea how would I pass a ref from Root down to SelectInput's menu. Don't know what `useForkRef` does, and never in my life used propTypes.
But I can try)
Has there... | 2022-09-08 16:15:09+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Select/Select.test.js-><Select /> prop: SelectDisplayProps should apply additional props to trigger element', 'packages/mui-material/src/Select/Select.test.js-><Select /> prop: onChange should not be called if selected element has the current value (value did not change)', 'packages/mui-mate... | ['packages/mui-material/src/Select/Select.test.js-><Select /> prop: autoWidth should take the trigger parent element width into account by default'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Select/Select.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,245 | mui__material-ui-34245 | ['34227'] | 7e7435ad08ba02a0e1d8d8676a519b8ded634149 | diff --git a/packages/mui-material/src/Fab/Fab.js b/packages/mui-material/src/Fab/Fab.js
--- a/packages/mui-material/src/Fab/Fab.js
+++ b/packages/mui-material/src/Fab/Fab.js
@@ -6,7 +6,7 @@ import ButtonBase from '../ButtonBase';
import capitalize from '../utils/capitalize';
import useThemeProps from '../styles/useT... | diff --git a/packages/mui-material/src/Fab/Fab.test.js b/packages/mui-material/src/Fab/Fab.test.js
--- a/packages/mui-material/src/Fab/Fab.test.js
+++ b/packages/mui-material/src/Fab/Fab.test.js
@@ -142,6 +142,13 @@ describe('<Fab />', () => {
expect(button.querySelector('.pulsate-focus-visible')).to.equal(null);
... | [Fab] button disabled class (classes.disabled) is not working.
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
css for classes.disabled is not honored when the Fab button is disabled
### Expected behavior 🤔
css for classe... | Probably, fab button needs to have the classes forwarded to buttonbase, just like button - https://github.com/mui/material-ui/blob/master/packages/mui-material/src/Button/Button.js#L36 ?
It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://materia... | 2022-09-09 13:27:25+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Fab/Fab.test.js-><Fab /> should render a primary floating action button', 'packages/mui-material/src/Fab/Fab.test.js-><Fab /> MUI component API ref attaches the ref', 'packages/mui-material/src/Fab/Fab.test.js-><Fab /> should render a success floating action button', 'packages/mui-material/s... | ['packages/mui-material/src/Fab/Fab.test.js-><Fab /> should pass disabled class to ButtonBase'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Fab/Fab.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,247 | mui__material-ui-34247 | ['34230'] | 6006aa39784a81fdfa0eb96bd2001b3eb86bd829 | diff --git a/packages/mui-material/src/Chip/Chip.js b/packages/mui-material/src/Chip/Chip.js
--- a/packages/mui-material/src/Chip/Chip.js
+++ b/packages/mui-material/src/Chip/Chip.js
@@ -13,7 +13,7 @@ import styled from '../styles/styled';
import chipClasses, { getChipUtilityClass } from './chipClasses';
const useU... | diff --git a/packages/mui-material/src/Chip/Chip.test.js b/packages/mui-material/src/Chip/Chip.test.js
--- a/packages/mui-material/src/Chip/Chip.test.js
+++ b/packages/mui-material/src/Chip/Chip.test.js
@@ -12,8 +12,9 @@ import {
} from 'test/utils';
import Avatar from '@mui/material/Avatar';
import Chip, { chipClas... | [Chip] icon `color` prop doesn't work inside Chip
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
`<Chip icon={<FaceIcon color="error" />} label="Label" />` creates a __gray__ icon.
### Expected behavior 🤔
`... | null | 2022-09-09 14:10:53+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Chip/Chip.test.js-><Chip /> prop: size should render the label with the labelSmall class', 'packages/mui-material/src/Chip/Chip.test.js-><Chip /> MUI component API prop: component can render another root component with the `component` prop', "packages/mui-material/src/Chip/Chip.test.js-><Chi... | ["packages/mui-material/src/Chip/Chip.test.js-><Chip /> prop: icon should not override the icon's custom color"] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,337 | mui__material-ui-34337 | ['32870'] | b3548fabeab1980d3c5e5b85945550df95ee6b82 | diff --git a/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.tsx b/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.tsx
--- a/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.tsx
+++ b/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.tsx
@@ -86,7 +86,8 @@ const ButtonUnstyled = React.forwardRef(function Bu... | diff --git a/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx b/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx
--- a/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx
+++ b/packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx
@@ -147,4 +147,38 @@ describe('<ButtonUnstyled />... | [ButtonUnstyled] Render as `a` if `href` prop is provided
If neither `component`, nor `components.Root` are provided and `href` or `to` props are present, the default rendered element should be `a` instead of `button` (as per https://github.com/mui/material-ui/pull/32403#pullrequestreview-976943341).
| null | 2022-09-16 13:20:16+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx-><ButtonUnstyled /> prop: focusableWhenDisabled as non-button element has aria-disabled and tabIndex attributes set', 'packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx-><ButtonUnstyled /> MUI unstyled component API uses the component provided in... | ['packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx-><ButtonUnstyled /> prop: to renders as a link when the "to" prop is provided', 'packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx-><ButtonUnstyled /> prop: href renders as a link when the "href" prop is provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/ButtonUnstyled/ButtonUnstyled.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,437 | mui__material-ui-34437 | ['34438'] | d9e863562f735bc798adfe20a63faa919a4fddd4 | diff --git a/packages/mui-system/src/colorManipulator.js b/packages/mui-system/src/colorManipulator.js
--- a/packages/mui-system/src/colorManipulator.js
+++ b/packages/mui-system/src/colorManipulator.js
@@ -189,7 +189,10 @@ export function hslToRgb(color) {
export function getLuminance(color) {
color = decomposeCol... | diff --git a/packages/mui-system/src/colorManipulator.test.js b/packages/mui-system/src/colorManipulator.test.js
--- a/packages/mui-system/src/colorManipulator.test.js
+++ b/packages/mui-system/src/colorManipulator.test.js
@@ -199,6 +199,14 @@ describe('utils/colorManipulator', () => {
expect(getLuminance('rgb(2... | getLuminance doesn't work with hsla colors
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
`getLuminance` doesn't seem to handle `hsla(..)` colors correctly. For example, `getLuminance("hsla(0, 0%, 100%, 1)")` returns `0.0... | null | 2022-09-22 18:16:22+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/colorManipulator.test.js->utils/colorManipulator decomposeColor idempotent', 'packages/mui-system/src/colorManipulator.test.js->utils/colorManipulator colorChannel converts hsl to a color channel` ', "packages/mui-system/src/colorManipulator.test.js->utils/colorManipulator lighten doesn't over... | ['packages/mui-system/src/colorManipulator.test.js->utils/colorManipulator getLuminance returns a valid luminance for hsla white', 'packages/mui-system/src/colorManipulator.test.js->utils/colorManipulator getLuminance returns a valid luminance for hsla black', 'packages/mui-system/src/colorManipulator.test.js->utils/co... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/colorManipulator.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-system/src/colorManipulator.js->program->function_declaration:getLuminance"] |
mui/material-ui | 34,445 | mui__material-ui-34445 | ['34404'] | 82d5d37106179635e7ed9c0efd962139ff62b5ea | diff --git a/packages/mui-material/src/Popover/Popover.js b/packages/mui-material/src/Popover/Popover.js
--- a/packages/mui-material/src/Popover/Popover.js
+++ b/packages/mui-material/src/Popover/Popover.js
@@ -374,6 +374,7 @@ const Popover = React.forwardRef(function Popover(inProps, ref) {
{...PaperProps}
... | diff --git a/packages/mui-material/src/Popover/Popover.test.js b/packages/mui-material/src/Popover/Popover.test.js
--- a/packages/mui-material/src/Popover/Popover.test.js
+++ b/packages/mui-material/src/Popover/Popover.test.js
@@ -7,6 +7,7 @@ import Grow from '@mui/material/Grow';
import Modal from '@mui/material/Moda... | [Menu] ownerState is undefined when the Menu is opened
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
You can check here. When you click DASHBOARD button and error occurs.
https://codesandbox.io/s/amazing-dubinsky-pkesu9... | `ownerState` is missing in Popover.
```diff
diff --git a/packages/mui-material/src/Popover/Popover.js b/packages/mui-material/src/Popover/Popover.js
index f35d551f64..15812e8ede 100644
--- a/packages/mui-material/src/Popover/Popover.js
+++ b/packages/mui-material/src/Popover/Popover.js
@@ -374,6 +374,7 @@ const... | 2022-09-23 13:51:01+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Popover/Popover.test.js-><Popover /> positioning when `marginThreshold=18` left < marginThreshold', 'packages/mui-material/src/Popover/Popover.test.js-><Popover /> positioning on an anchor should be positioned over the bottom left of the anchor', 'packages/mui-material/src/Popover/Popover.te... | ["packages/mui-material/src/Popover/Popover.test.js-><Popover /> should not throw if ownerState is used in slot's styleOverrides"] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Popover/Popover.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,455 | mui__material-ui-34455 | ['34425'] | 2890881a35de8bd364ccc7cab4fb7c2c227b130f | diff --git a/packages/mui-joy/src/Chip/Chip.tsx b/packages/mui-joy/src/Chip/Chip.tsx
--- a/packages/mui-joy/src/Chip/Chip.tsx
+++ b/packages/mui-joy/src/Chip/Chip.tsx
@@ -215,7 +215,6 @@ const Chip = React.forwardRef(function Chip(inProps, ref) {
const ownerState: ChipOwnerState = {
...props,
component,
- ... | diff --git a/packages/mui-joy/src/Chip/Chip.test.js b/packages/mui-joy/src/Chip/Chip.test.js
--- a/packages/mui-joy/src/Chip/Chip.test.js
+++ b/packages/mui-joy/src/Chip/Chip.test.js
@@ -1,6 +1,7 @@
import * as React from 'react';
import { expect } from 'chai';
-import { createRenderer, describeConformance } from 'te... | [Joy][Chip] `onClick` is not working
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Steps:
1. Go to https://codesandbox.io/s/winter-cloud-2it1xn?file=/demo.js
2. Try to click on the chip. Nothing happens.
3. Try to c... | Even the official example in the doc is not working:
https://mui.com/joy-ui/react-chip/#clickable-and-deletable
Clicking on the delete icons works, but not on the chip itself.
Looks like a bug to me. | 2022-09-24 15:54:10+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-joy/src/Chip/Chip.test.js-><Chip /> prop: disabled renders as a disabled chip when `disabled` is `true`', 'packages/mui-joy/src/Chip/Chip.test.js-><Chip /> MUI component API ref attaches the ref', 'packages/mui-joy/src/Chip/Chip.test.js-><Chip /> MUI component API spreads props to the root component', 'p... | ['packages/mui-joy/src/Chip/Chip.test.js-><Chip /> clickable should call onClick'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,477 | mui__material-ui-34477 | ['34411'] | 17695ff6be0aa6c7e4c81cadee5b9c8fb0c1a0b8 | diff --git a/packages/mui-joy/src/Checkbox/Checkbox.tsx b/packages/mui-joy/src/Checkbox/Checkbox.tsx
--- a/packages/mui-joy/src/Checkbox/Checkbox.tsx
+++ b/packages/mui-joy/src/Checkbox/Checkbox.tsx
@@ -202,7 +202,9 @@ const Checkbox = React.forwardRef(function Checkbox(inProps, ref) {
onChange,
onFocus,
... | diff --git a/packages/mui-joy/src/Checkbox/Checkbox.test.js b/packages/mui-joy/src/Checkbox/Checkbox.test.js
--- a/packages/mui-joy/src/Checkbox/Checkbox.test.js
+++ b/packages/mui-joy/src/Checkbox/Checkbox.test.js
@@ -34,6 +34,18 @@ describe('<Checkbox />', () => {
expect(getByRole('checkbox')).to.have.property('... | [Joy][Checkbox] Checkbox not have 'value' props
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Joy UI Checkbox not have 'value' props. When there is value props, TypeScript got anger.
### Current behavior 😯
_No respons... | Thanks for reporting the issue! will fix it asap. | 2022-09-26 07:10:40+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-joy/src/Checkbox/Checkbox.test.js-><Checkbox /> prop: indeterminate should render an indeterminate icon', 'packages/mui-joy/src/Checkbox/Checkbox.test.js-><Checkbox /> the checkbox can be disabled', 'packages/mui-joy/src/Checkbox/Checkbox.test.js-><Checkbox /> renders a checkbox with the Checked state wh... | ['packages/mui-joy/src/Checkbox/Checkbox.test.js-><Checkbox /> prop: indeterminate should have aria-checked="mixed"', 'packages/mui-joy/src/Checkbox/Checkbox.test.js-><Checkbox /> renders a `role="checkbox"` with readOnly attribute', 'packages/mui-joy/src/Checkbox/Checkbox.test.js-><Checkbox /> renders a `role="checkbo... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/Checkbox/Checkbox.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,478 | mui__material-ui-34478 | ['34410'] | 17695ff6be0aa6c7e4c81cadee5b9c8fb0c1a0b8 | diff --git a/packages/mui-joy/src/Radio/Radio.tsx b/packages/mui-joy/src/Radio/Radio.tsx
--- a/packages/mui-joy/src/Radio/Radio.tsx
+++ b/packages/mui-joy/src/Radio/Radio.tsx
@@ -236,6 +236,7 @@ const Radio = React.forwardRef(function Radio(inProps, ref) {
onChange,
onFocus,
onFocusVisible,
+ readOnly... | diff --git a/packages/mui-joy/src/Radio/Radio.test.js b/packages/mui-joy/src/Radio/Radio.test.js
--- a/packages/mui-joy/src/Radio/Radio.test.js
+++ b/packages/mui-joy/src/Radio/Radio.test.js
@@ -35,6 +35,18 @@ describe('<Radio />', () => {
expect(getByRole('radio')).to.have.property('name', 'bar');
});
+ it(... | [Joy][Radio] `required` prop does not work
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
When joy ui Radio compoment has required props, it can't passing down to `<input type="radio"/>` .
### Current behavior 😯
_No ... | null | 2022-09-26 07:19:17+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ["packages/mui-joy/src/Radio/Radio.test.js-><Radio /> MUI component API theme default components: respect theme's defaultProps", 'packages/mui-joy/src/Radio/Radio.test.js-><Radio /> the Checked state changes after change events', 'packages/mui-joy/src/Radio/Radio.test.js-><Radio /> MUI component API applies the root cl... | ['packages/mui-joy/src/Radio/Radio.test.js-><Radio /> renders a `role="radio"` with the required attribute', 'packages/mui-joy/src/Radio/Radio.test.js-><Radio /> renders a `role="radio"` with the readOnly attribute'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/Radio/Radio.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,548 | mui__material-ui-34548 | ['31203'] | 139724acb3ff53e7f4c8a3a3be90d004f8b8309f | diff --git a/packages/mui-system/src/palette.js b/packages/mui-system/src/palette.js
--- a/packages/mui-system/src/palette.js
+++ b/packages/mui-system/src/palette.js
@@ -1,20 +1,30 @@
import style from './style';
import compose from './compose';
+function transform(value, userValue) {
+ if (userValue === 'grey') ... | diff --git a/packages/mui-system/src/palette.test.js b/packages/mui-system/src/palette.test.js
new file mode 100644
--- /dev/null
+++ b/packages/mui-system/src/palette.test.js
@@ -0,0 +1,30 @@
+import { expect } from 'chai';
+import palette from './palette';
+
+const theme = {
+ palette: {
+ grey: { 100: '#f5f5f5' ... | [system] `grey` is no more recognized as color with the sx prop
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
I migrating project from v4 to v5
`backgroundColor:"grey"` doesn't work anymore with SX style. I ha... | The `grey` is part of the palette, so the `sx` prop will try to use the value from the palette if provided. However, in this case the value provided is an object, which is not a valid CSS property. You should use `grey.100` or any other palette value, for example: https://codesandbox.io/s/69629346-mui-v5-theming-with-e... | 2022-10-01 20:55:20+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/palette.test.js->palette should treat grey.100 as theme color'] | ['packages/mui-system/src/palette.test.js->palette should treat grey as CSS color'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/palette.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/mui-system/src/style.js->program->function_declaration:getValue", "packages/mui-system/src/palette.js->program->function_declaration:transform"] |
mui/material-ui | 34,610 | mui__material-ui-34610 | ['34604'] | 1e09429e1804ddd7505fe78f3d606e24e98aa16f | diff --git a/packages/mui-base/src/SliderUnstyled/SliderUnstyled.js b/packages/mui-base/src/SliderUnstyled/SliderUnstyled.js
--- a/packages/mui-base/src/SliderUnstyled/SliderUnstyled.js
+++ b/packages/mui-base/src/SliderUnstyled/SliderUnstyled.js
@@ -46,6 +46,7 @@ const SliderUnstyled = React.forwardRef(function Slider... | diff --git a/packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js b/packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js
--- a/packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js
+++ b/packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js
@@ -282,4 +282,47 @@ describe('<SliderUnstyled />', (... | [Slider] Accessibility: `aria-labelledby` is passed into outer `span` and `input` elements
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Use `<Slider />` and pass `aria-labelledby` attribute
Here is a codesandbox:
h... | null | 2022-10-04 19:43:57+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js-><SliderUnstyled /> MUI unstyled component API merges the class names provided in componentsProps.track with the built-in ones', 'packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js-><SliderUnstyled /> MUI unstyled component API allows overriding the... | ['packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js-><SliderUnstyled /> ARIA should have the correct aria attributes'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/SliderUnstyled/SliderUnstyled.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 34,966 | mui__material-ui-34966 | ['34965'] | 8f246c16a78968aec03a13835bc5c7c74ea3d945 | diff --git a/docs/data/material/components/dividers/DividerText.js b/docs/data/material/components/dividers/DividerText.js
--- a/docs/data/material/components/dividers/DividerText.js
+++ b/docs/data/material/components/dividers/DividerText.js
@@ -6,7 +6,7 @@ import Chip from '@mui/material/Chip';
const Root = styled('... | diff --git a/packages/mui-system/src/Stack/Stack.test.js b/packages/mui-system/src/Stack/Stack.test.js
--- a/packages/mui-system/src/Stack/Stack.test.js
+++ b/packages/mui-system/src/Stack/Stack.test.js
@@ -29,21 +29,21 @@ describe('<Stack />', () => {
}),
).to.deep.equal({
'@media (min-width:0px)': ... | [Stack] doesn't space children correctly when there are style tags between them
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/unruffled-pine-lnym3m?file=/src/App.tsx
Step... | null | 2022-10-31 14:54:15+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/Stack/Stack.test.js-><Stack /> prop: direction should generate correct direction even though breakpoints are not fully provided', 'packages/mui-system/src/Stack/Stack.test.js-><Stack /> MUI component API applies the className to the root component', 'packages/mui-system/src/Stack/Stack.test.js... | ['packages/mui-system/src/Stack/Stack.test.js-><Stack /> should handle spacing with multiple keys and null values', 'packages/mui-system/src/Stack/Stack.test.js-><Stack /> should handle flat params', 'packages/mui-system/src/Stack/Stack.test.js-><Stack /> prop: spacing should generate correct responsive styles regardle... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/Stack/Stack.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/data/material/components/links/UnderlineLink.js->program->function_declaration:UnderlineLink", "docs/data/material/components/links/Links.js->program->function_declaration:Links"] |
mui/material-ui | 35,178 | mui__material-ui-35178 | ['35159'] | 1ea442da69a48694c3880e1302cfc10eb85e93eb | diff --git a/packages/mui-material/src/styles/experimental_extendTheme.js b/packages/mui-material/src/styles/experimental_extendTheme.js
--- a/packages/mui-material/src/styles/experimental_extendTheme.js
+++ b/packages/mui-material/src/styles/experimental_extendTheme.js
@@ -1,10 +1,10 @@
import { deepmerge } from '@mu... | diff --git a/packages/mui-material/src/styles/experimental_extendTheme.test.js b/packages/mui-material/src/styles/experimental_extendTheme.test.js
--- a/packages/mui-material/src/styles/experimental_extendTheme.test.js
+++ b/packages/mui-material/src/styles/experimental_extendTheme.test.js
@@ -409,4 +409,54 @@ describe... | Allow using linear-gradient color in theme palette
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
Allow using linear-gradient color in theme palette or allow to use it if it is non-default palette
### Examples 🌈
I t... | I see that the docs are lacking this info. We should mention that the `palette.*.(light|main|dark)` will be used to calculate channel colors (I think this should be fixed to only apply to the default palette)
@vimutti77 to make the background works, you need to use `background`, not `bgcolor` (this is how CSS works)... | 2022-11-17 03:33:40+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme should generate color channels', 'packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme shadows should provide the default array', 'packages/mui-material/src/styles/experimental_extendThem... | ['packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme warnings dependent token: should warn if the value cannot be parsed by color manipulators', 'packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme warnings custom palette should not throw ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/styles/experimental_extendTheme.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 6 | 0 | 6 | false | false | ["packages/mui-system/src/colorManipulator.js->program->function_declaration:private_safeLighten", "packages/mui-material/src/styles/experimental_extendTheme.js->program->function_declaration:extendTheme", "packages/mui-system/src/colorManipulator.js->program->function_declaration:private_safeEmphasize", "packages/mui-... |
mui/material-ui | 35,196 | mui__material-ui-35196 | ['30178'] | d0c2ee1e772fc1e2b043fe274ee269f0c169782a | diff --git a/packages/mui-base/src/useAutocomplete/useAutocomplete.js b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
--- a/packages/mui-base/src/useAutocomplete/useAutocomplete.js
+++ b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
@@ -965,12 +965,15 @@ export default function useAutocomplete(pro... | diff --git a/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx b/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
--- a/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
+++ b/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
@@ -2049,7 +2049,7 @@ describe('Joy <Autocomplete />', () => {
... | [Autocomplete] cursor resets highlighted item when using arrow keys
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
I begin with my mouse hovering over the first item. When I reach the bottom of the list (navigating via d-pa... | This indeed could be considered a bug, but I would say it's low priority. Firstly, the workaround is pretty simple (moving the mouse). Secondly, we are working on a change in Autocomplete internals that will be free of this issue. It likely won't be released before the next major version, though.
We may reconsider wor... | 2022-11-18 14:05:25+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: onHighlightChange should pass to onHighlightChange the correct value after filtering', 'packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: disabled should disable the input', 'packages/mui-material/src... | ['packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: onHighlightChange should support mouse event', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: onHighlightChange should support mouse event'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha test/e2e/index.test.ts packages/mui-material/src/Autocomplete/Autocomplete.test.js test/e2e/fixtures/Autocomplete/HoverMaterialAutocomplete.tsx test/e2e/fixtures/Autocomplete/HoverJoyAutocomplete.tsx packages/mui-joy/src/Autocomplete/Autocom... | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 35,364 | mui__material-ui-35364 | ['35363'] | 9e140a77ebd8464e2b400b1d1d19fc63c387a864 | diff --git a/packages/mui-utils/src/deepmerge.ts b/packages/mui-utils/src/deepmerge.ts
--- a/packages/mui-utils/src/deepmerge.ts
+++ b/packages/mui-utils/src/deepmerge.ts
@@ -6,6 +6,20 @@ export interface DeepmergeOptions {
clone?: boolean;
}
+function deepClone<T>(source: T): T | Record<keyof any, unknown> {
+ ... | diff --git a/packages/mui-utils/src/deepmerge.test.ts b/packages/mui-utils/src/deepmerge.test.ts
--- a/packages/mui-utils/src/deepmerge.test.ts
+++ b/packages/mui-utils/src/deepmerge.test.ts
@@ -45,4 +45,19 @@ describe('deepmerge', () => {
bar: 'test',
});
});
+
+ it('should deep clone source key object... | [Utils/deepmerge] target key assigns a reference to the source key object if the target key does not exist.
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
[Codesandbox
](https://codesandbox.io/s/m... | null | 2022-12-05 22:26:11+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-utils/src/deepmerge.test.ts->deepmerge should not merge HTML elements', 'packages/mui-utils/src/deepmerge.test.ts->deepmerge should reset source when target is undefined', 'packages/mui-utils/src/deepmerge.test.ts->deepmerge should not be subject to prototype pollution', 'packages/mui-utils/src/deepmerge... | ['packages/mui-utils/src/deepmerge.test.ts->deepmerge should deep clone source key object if target key does not exist'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-utils/src/deepmerge.test.ts --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/mui-utils/src/deepmerge.ts->program->function_declaration:deepmerge", "packages/mui-utils/src/deepmerge.ts->program->function_declaration:deepClone"] |
mui/material-ui | 35,410 | mui__material-ui-35410 | ['35164'] | 1e4dd5f0837c84a4f1a55590857f989d6c3198fc | diff --git a/packages/mui-base/src/ButtonUnstyled/useButton.ts b/packages/mui-base/src/ButtonUnstyled/useButton.ts
--- a/packages/mui-base/src/ButtonUnstyled/useButton.ts
+++ b/packages/mui-base/src/ButtonUnstyled/useButton.ts
@@ -91,21 +91,20 @@ export default function useButton(parameters: UseButtonParameters) {
}... | diff --git a/packages/mui-base/src/ButtonUnstyled/useButton.test.tsx b/packages/mui-base/src/ButtonUnstyled/useButton.test.tsx
--- a/packages/mui-base/src/ButtonUnstyled/useButton.test.tsx
+++ b/packages/mui-base/src/ButtonUnstyled/useButton.test.tsx
@@ -41,6 +41,46 @@ describe('useButton', () => {
fireEvent.k... | [ButtonUnstyled] cannot trigger active status when click element inside button
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
https://stackblitz.com/edit/react-d7kdwv-qqwmf4?file=demo.js
Steps:
... | null | 2022-12-09 13:13:08+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/ButtonUnstyled/useButton.test.tsx->useButton state: active event handlers calls them when provided in props', 'packages/mui-base/src/ButtonUnstyled/useButton.test.tsx->useButton state: active when using a button element is set when triggered by mouse', 'packages/mui-base/src/ButtonUnstyled/useBu... | ['packages/mui-base/src/ButtonUnstyled/useButton.test.tsx->useButton state: active when using a button element is unset when mouse button is released above another element', 'packages/mui-base/src/ButtonUnstyled/useButton.test.tsx->useButton state: active when using a button element is set when clicked on an element in... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/ButtonUnstyled/useButton.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/ButtonUnstyled/useButton.ts->program->function_declaration:useButton"] |
mui/material-ui | 35,477 | mui__material-ui-35477 | ['34214'] | e195455738a9de164d1f9766de96213b83dd6623 | diff --git a/packages/mui-utils/src/resolveProps.ts b/packages/mui-utils/src/resolveProps.ts
--- a/packages/mui-utils/src/resolveProps.ts
+++ b/packages/mui-utils/src/resolveProps.ts
@@ -4,14 +4,43 @@
* @param {object} props
* @returns {object} resolved props
*/
-export default function resolveProps<T extends { c... | diff --git a/packages/mui-utils/src/resolveProps.test.ts b/packages/mui-utils/src/resolveProps.test.ts
--- a/packages/mui-utils/src/resolveProps.test.ts
+++ b/packages/mui-utils/src/resolveProps.test.ts
@@ -44,4 +44,51 @@ describe('resolveProps', () => {
foo: '',
});
});
+
+ it('merge components and com... | `slots` overrides do not merge with the theme
## Problem
### How does the theme default props work
Users can define default props for there components using the theme as follow:
```tsx
const theme = createTheme({
components: {
MuiDatePicker: {
defaultProps: {
closeOnSelect: true,
... | In general, this makes sense to me. We can do a POC with Joy UI in the next quarter together with the Data Grid integration.
Would you consider it a breaking change ? Technically it's a behavior change but I don't know who would currently use the theme to define `components` and expect the current behavior.
> Would you... | 2022-12-14 10:35:32+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-utils/src/resolveProps.test.ts->resolveProps "" is a considered a valid value', 'packages/mui-utils/src/resolveProps.test.ts->resolveProps should not merge props that are not intended', 'packages/mui-utils/src/resolveProps.test.ts->resolveProps use props if defined', 'packages/mui-utils/src/resolveProps.... | ['packages/mui-utils/src/resolveProps.test.ts->resolveProps merge components and componentsProps props', 'packages/mui-utils/src/resolveProps.test.ts->resolveProps merge slots and slotProps props'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-utils/src/resolveProps.test.ts --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-utils/src/resolveProps.ts->program->function_declaration:resolveProps"] |
mui/material-ui | 35,804 | mui__material-ui-35804 | ['35768'] | 0486f4b2952519d9a01c17dc45841523acdd7f92 | diff --git a/packages/mui-material/src/styles/experimental_extendTheme.js b/packages/mui-material/src/styles/experimental_extendTheme.js
--- a/packages/mui-material/src/styles/experimental_extendTheme.js
+++ b/packages/mui-material/src/styles/experimental_extendTheme.js
@@ -34,6 +34,19 @@ function setColor(obj, key, de... | diff --git a/packages/mui-material/src/styles/experimental_extendTheme.test.js b/packages/mui-material/src/styles/experimental_extendTheme.test.js
--- a/packages/mui-material/src/styles/experimental_extendTheme.test.js
+++ b/packages/mui-material/src/styles/experimental_extendTheme.test.js
@@ -423,10 +423,37 @@ describ... | Suppress error message for MUI color value
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
I'm in the process of extending my style system for dark mode. I found it much easier to supply CSS variables to a single palette th... | @R-Bower Thanks for the feedback. The reason you see the warning is that Material UI can't generate a channel token from the background.
By default, the `backgroundChannel` token is generated because some components need to use translucent color:
```js
// default theme
--mui-palette-background-default: #fff;
-... | 2023-01-12 06:38:43+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme should generate color channels', 'packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme shadows should provide the default array', 'packages/mui-material/src/styles/experimental_extendThem... | ['packages/mui-material/src/styles/experimental_extendTheme.test.js->experimental_extendTheme warnings dependent token: should warn if the value cannot be parsed by color manipulators'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/styles/experimental_extendTheme.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/mui-material/src/styles/experimental_extendTheme.js->program->function_declaration:extendTheme", "packages/mui-material/src/styles/experimental_extendTheme.js->program->function_declaration:setColorChannel"] |
mui/material-ui | 35,838 | mui__material-ui-35838 | ['35780'] | 0198612f091c8d52310717106f234c81199d4d35 | diff --git a/packages/mui-base/src/ListboxUnstyled/useListbox.ts b/packages/mui-base/src/ListboxUnstyled/useListbox.ts
--- a/packages/mui-base/src/ListboxUnstyled/useListbox.ts
+++ b/packages/mui-base/src/ListboxUnstyled/useListbox.ts
@@ -267,7 +267,7 @@ export default function useListbox<TOption>(props: UseListboxPara... | diff --git a/packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx b/packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx
--- a/packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx
+++ b/packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx
@@ -1,5 +1,6 @@
import * as React from 'react';
import { expect... | [Joy][Menu] Scrollable menu jumps to end and back to start on load
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/k0zipv?file=/demo.tsx
Steps:
1. Open a menu with scrol... | null | 2023-01-15 22:19:00+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ["packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx->MenuUnstyled MUI unstyled component API sets custom properties on the root slot's element", "packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx->MenuUnstyled MUI unstyled component API sets custom properties on the root slot's element with a callback fun... | ['packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx->MenuUnstyled after initialization highlights the first item when the menu is opened'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/MenuUnstyled/MenuUnstyled.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/ListboxUnstyled/useListbox.ts->program->function_declaration:useListbox"] |
mui/material-ui | 35,994 | mui__material-ui-35994 | ['35959'] | 2694045ca3d1273cfa1a3415c6ce4b971b298f7a | diff --git a/docs/data/material/components/grid2/SpacingGrid.js b/docs/data/material/components/grid2/SpacingGrid.js
--- a/docs/data/material/components/grid2/SpacingGrid.js
+++ b/docs/data/material/components/grid2/SpacingGrid.js
@@ -1,4 +1,5 @@
import * as React from 'react';
+import Box from '@mui/material/Box';
i... | diff --git a/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js b/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
--- a/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
+++ b/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
@@ -239,33 +239,39 @@ describe('grid generator', () =... | Unstable_Grid2 cannot override spacing in Nested Grid
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/optimistic-waterfall-qhrh60?file=/src/App.tsx
### Current b... | I can reproduce it. There is no need to have `disableSpacingInheritance`. The `spacing={0}` should work. | 2023-01-30 06:15:40+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator traverse breakpoints supports array', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridOffsetStyles supports responsive object', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid genera... | ['packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridStyles item with disableEqualOverflow', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridStyles root container with disableEqualOverflow', 'packages/mui-system/src/Unstable_Grid/gridGenerato... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/Unstable_Grid/gridGenerator.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:createGetSelfSpacing", "packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:createGetParentSpacing", "packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:isNestedCo... |
mui/material-ui | 36,024 | mui__material-ui-36024 | ['34731'] | 910d3a4ca46c6f79b7b5507c35532774c38460d2 | diff --git a/docs/data/material/components/selects/selects.md b/docs/data/material/components/selects/selects.md
--- a/docs/data/material/components/selects/selects.md
+++ b/docs/data/material/components/selects/selects.md
@@ -127,6 +127,67 @@ Display categories with the `ListSubheader` component or the native `<optgro... | diff --git a/packages/mui-material/src/Select/Select.test.js b/packages/mui-material/src/Select/Select.test.js
--- a/packages/mui-material/src/Select/Select.test.js
+++ b/packages/mui-material/src/Select/Select.test.js
@@ -10,7 +10,7 @@ import {
screen,
} from 'test/utils';
import { createTheme, ThemeProvider } fr... | [Select] First option chosen as selected when grouping with ListSubheader
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
https://codesandbox.io/s/eloquent-architecture-in71n1 - It's a simple grouping.
### Cur... | This is a regression introduced in https://github.com/mui/material-ui/pull/27299. We should not add the item as `selected`. cc @michaldudak could you verify that the linked PR was indeed wrong? In my opinion, we should have just focused that element.
Yes, it seems that it's incorrectly selecting the first element in th... | 2023-02-01 21:59:16+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Select/Select.test.js-><Select /> prop: SelectDisplayProps should apply additional props to trigger element', 'packages/mui-material/src/Select/Select.test.js-><Select /> prop: onChange should not be called if selected element has the current value (value did not change)', 'packages/mui-mate... | ['packages/mui-material/src/Select/Select.test.js-><Select /> should not have the selectable option selected when inital value provided is empty string on Select with ListSubHeader item'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Select/Select.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 36,056 | mui__material-ui-36056 | ['36054'] | 1dc2782ddd66e3642ffc2175015d0af6de494a52 | diff --git a/docs/data/material/components/use-media-query/use-media-query.md b/docs/data/material/components/use-media-query/use-media-query.md
--- a/docs/data/material/components/use-media-query/use-media-query.md
+++ b/docs/data/material/components/use-media-query/use-media-query.md
@@ -94,9 +94,9 @@ describe('MyTes... | diff --git a/packages/mui-material/src/useMediaQuery/useMediaQuery.test.js b/packages/mui-material/src/useMediaQuery/useMediaQuery.test.js
--- a/packages/mui-material/src/useMediaQuery/useMediaQuery.test.js
+++ b/packages/mui-material/src/useMediaQuery/useMediaQuery.test.js
@@ -144,7 +144,7 @@ describe('useMediaQuery',... | [useMediaQuery] Regression noSsr: true has no longer any impact
### Steps to reproduce 🕹
Link to live example:
Steps:
1. Open https://stackblitz.com/edit/nextjs-3tuoz5?file=pages%2Findex.js,package.json
2. Check the console logs
```tsx
import * as React from 'react';
import useMediaQuery from '@mui/mate... | null | 2023-02-04 16:46:54+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery server-side should use the ssr match media ponyfill', 'packages/mui-material/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery with window.matchMedia option: defaultMatches should take the option into account', 'packages/mui-material/sr... | ['packages/mui-material/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery with window.matchMedia option: noSsr hydrate API: should render once if the default value does not match the expectation but `noSsr` is enabled'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/useMediaQuery/useMediaQuery.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/mui-material/src/useMediaQuery/useMediaQuery.ts->program->function_declaration:useMediaQueryNew", "packages/mui-material/src/useMediaQuery/useMediaQuery.ts->program->function_declaration:useMediaQueryOld", "packages/mui-material/src/useMediaQuery/useMediaQuery.ts->program->function_declaration:useMediaQuery"... |
mui/material-ui | 36,088 | mui__material-ui-36088 | ['36045'] | b1d2e8d375be4f2a238fe7bce81ad2bf5cb68ad1 | diff --git a/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js b/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js
--- a/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js
+++ b/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js
@@ -465,6 +465,12 @@ export default function ... | diff --git a/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx b/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
--- a/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
+++ b/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
@@ -1975,6 +1975,25 @@ describe('Joy <Autocomplete />', () => {
... | [Autocomplete] Non-freesolo autocomplete acts like freesolo: passes string to `getOptionLabel` instead of option
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Steps:
1. Make a normal auto-complete (not free so... | It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://mui.com/r/issue-template), a link to a repository on GitHub, or provide a proper minimal code example that reproduces the problem.
@ZeeshanTamboli I literally did provide enough info. That is no ... | 2023-02-07 10:15:25+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: onHighlightChange should pass to onHighlightChange the correct value after filtering', 'packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: disabled should disable the input', 'packages/mui-material/src... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: getOptionLabel should not throw error when nested options are provided', 'packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: getOptionLabel should not throw error when nested options are provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 36,116 | mui__material-ui-36116 | ['36114'] | f800c835562da9cc8fa3f7615b32a8e6cc8b31d8 | diff --git a/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js b/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js
--- a/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js
+++ b/packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js
@@ -470,7 +470,8 @@ export default function u... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -2822,4 +2822,57 @@ describe('<Autocomplete />', (... | [Autocomplete] 5.11.7 Introduced a Crashing Bug For This Configuration of Autocomplete
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/compassionate-kapitsa-ouc9ml?... | Thanks for the detailed report. We'll fix it ASAP. | 2023-02-09 10:33:02+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> deleting a tag immediately after adding it while the listbox is still open should allow it, given that options are primitive values', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> deleting a tag immediately ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/AutocompleteUnstyled/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 36,353 | mui__material-ui-36353 | ['36108'] | d57bd96cfcec023238c85488a3d399534518fd37 | diff --git a/packages/mui-material/src/DialogTitle/DialogTitle.js b/packages/mui-material/src/DialogTitle/DialogTitle.js
--- a/packages/mui-material/src/DialogTitle/DialogTitle.js
+++ b/packages/mui-material/src/DialogTitle/DialogTitle.js
@@ -37,7 +37,7 @@ const DialogTitle = React.forwardRef(function DialogTitle(inPro... | diff --git a/packages/mui-material/src/DialogTitle/DialogTitle.test.js b/packages/mui-material/src/DialogTitle/DialogTitle.test.js
--- a/packages/mui-material/src/DialogTitle/DialogTitle.test.js
+++ b/packages/mui-material/src/DialogTitle/DialogTitle.test.js
@@ -1,6 +1,8 @@
import * as React from 'react';
+import { ex... | [Dialog] Custom ID not reflecting on MUI `DialogTitle` component
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/polished-bush-8f33zj?file=/demo.js
### Current ... | It's a bug. Thanks for reporting. You are correct; it never uses the `id` prop provided to the `DialogTitle` component. It seems easy to fix. Would you like to create a PR?
Yes, I would love to fix it. Will create a pull request.
Hi, I can fix this. Can you assign it to me?
Hi. I can fix this. If its not fixed assign i... | 2023-02-26 04:18:36+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> MUI component API spreads props to the root component', "packages/mui-material/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> MUI component API theme default components: respect theme's defaultProps", 'packages/mui-material/src/DialogTit... | ['packages/mui-material/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> prop: id should apply the id attribute provided to the Dialog title', 'packages/mui-material/src/DialogTitle/DialogTitle.test.js-><DialogTitle /> prop: id should apply the id attribute explicitly provided to the DialogTitle and not take from D... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/DialogTitle/DialogTitle.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 36,399 | mui__material-ui-36399 | ['36777'] | fe7ac373c763867a0eb1eb5be8da09b303d9e417 | diff --git a/docs/data/material/components/grid2/grid2.md b/docs/data/material/components/grid2/grid2.md
--- a/docs/data/material/components/grid2/grid2.md
+++ b/docs/data/material/components/grid2/grid2.md
@@ -130,14 +130,21 @@ The demo below shows how this works:
## Nested grid
-The grid container that renders i... | diff --git a/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js b/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
--- a/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
+++ b/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
@@ -239,7 +239,7 @@ describe('grid generator', () => ... | [Grid][Dialog] Using grid and dialog together doesn't work
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/p/sandbox/romantic-drake-1oifhz
Steps:
There are 2 dialog:
- th... | null | 2023-03-02 11:24:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator traverse breakpoints supports array', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridOffsetStyles supports responsive object', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid genera... | ['packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridStyles root container with disableEqualOverflow', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridColumnSpacingStyles nested item level 1 should have default spacing set to parent', 'packag... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/Unstable_Grid/gridGenerator.test.js test/regressions/fixtures/Grid/StressNestedGrid2.js test/regressions/fixtures/Grid/StyledGrid2.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 5 | 0 | 5 | false | false | ["packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:createGetParentSpacing", "packages/mui-system/src/createStyled.js->program->function_declaration:createStyled", "packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:createGetSelfSpacing", "packages/... |
mui/material-ui | 36,401 | mui__material-ui-36401 | ['36335'] | b1b9ef7fae31cd34e3dc0be72439975f4a8bad6a | diff --git a/docs/data/material/components/grid2/NestedGridColumns.js b/docs/data/material/components/grid2/NestedGridColumns.js
new file mode 100644
--- /dev/null
+++ b/docs/data/material/components/grid2/NestedGridColumns.js
@@ -0,0 +1,44 @@
+import * as React from 'react';
+import { styled } from '@mui/material/styl... | diff --git a/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js b/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
--- a/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
+++ b/packages/mui-system/src/Unstable_Grid/gridGenerator.test.js
@@ -252,7 +252,7 @@ describe('grid generator', () => ... | Nested grids break custom column layout
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
I have a nested grid with the standard 12 columns in the outer grid and two children with widths 4 and 8 (4 + 8 = 12):
``... | @githorse Thanks for reporting this. The root cause is that the nested Grid does not use `--Grid-columns` value from the parent because it is overridden by its own `--Grid-columns`.
I will open a fix soon. | 2023-03-02 13:57:39+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator traverse breakpoints supports array', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridOffsetStyles supports responsive object', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid genera... | ['packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridStyles root container with disableEqualOverflow', 'packages/mui-system/src/Unstable_Grid/gridGenerator.test.js->grid generator generateGridColumnSpacingStyles nested item level 1 should have default spacing set to parent', 'packag... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/Unstable_Grid/gridGenerator.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:createGetSelfSpacing", "packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:getParentColumns", "packages/mui-system/src/Unstable_Grid/gridGenerator.ts->program->function_declaration:appendLevel", "p... |
mui/material-ui | 36,426 | mui__material-ui-36426 | ['26492'] | a0c6c43187da86b1538685afdb529971ef57932f | diff --git a/docs/pages/base-ui/api/use-autocomplete.json b/docs/pages/base-ui/api/use-autocomplete.json
--- a/docs/pages/base-ui/api/use-autocomplete.json
+++ b/docs/pages/base-ui/api/use-autocomplete.json
@@ -68,6 +68,12 @@
"description": "(option: Value) => boolean"
}
},
+ "getOptionKey": ... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -2654,6 +2654,27 @@ describe('<Autocomplete />', (... | [Autocomplete] Not working properly with repeated options values
## Current Behavior 😯
Autocomplete when receiving repeated options does not filter and does not work correctly
## Expected Behavior 🤔
This only happens in version 5, in version 4 this works correctly.
## Steps to Reproduce 🕹
Enter this C... | Thanks for the report.
> Autocomplete when receiving repeated options does not filter and does not work correctly
Could you be a bit more specific what you mean with "correctly"? What are the concrete differences between v4 and v5? A screen recording might help here.
> Thanks for the report.
>
> > Autocomplete... | 2023-03-04 22:34:31+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> should specify option key for duplicate options'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete", "packages/mui-base/src/useAutocomplete/useAutocomplete.spec.ts->program->function_declaration:Component->method_definition:getOptionKey", "packages/mui-base/src/useAutocomplete/useAutocomplete.spec.ts->program->f... |
mui/material-ui | 36,853 | mui__material-ui-36853 | ['36452'] | 44748d4c1f5272f00bb362af2869895ce8c28677 | diff --git a/packages/mui-system/src/cssVars/prepareCssVars.ts b/packages/mui-system/src/cssVars/prepareCssVars.ts
--- a/packages/mui-system/src/cssVars/prepareCssVars.ts
+++ b/packages/mui-system/src/cssVars/prepareCssVars.ts
@@ -38,9 +38,12 @@ function prepareCssVars<T extends DefaultCssVarsTheme, ThemeVars extends R... | diff --git a/packages/mui-system/src/cssVars/prepareCssVars.test.ts b/packages/mui-system/src/cssVars/prepareCssVars.test.ts
new file mode 100644
--- /dev/null
+++ b/packages/mui-system/src/cssVars/prepareCssVars.test.ts
@@ -0,0 +1,39 @@
+import { expect } from 'chai';
+import prepareCssVars from './prepareCssVars';
+
... | Overlay css variables are not present when `defaultMode="dark"`
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/recursing-monad-rg3n5v
Steps:
1. Open the link above, th... | @Pikachews I am not exactly sure what's the problem because your CodeSandbox is empty.
However, what you experienced is the expected behavior. Overlay variables are intended to be used in dark mode only so it works for `Paper` with elevation.
Anyway, could you fix the [Codesandbox](https://codesandbox.io/s/recurs... | 2023-04-12 04:21:38+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | [] | ['packages/mui-system/src/cssVars/prepareCssVars.test.ts->prepareCssVars delete css fields should not affect the next call', 'packages/mui-system/src/cssVars/prepareCssVars.test.ts->prepareCssVars `generateCssVars` should always return a new object'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/cssVars/prepareCssVars.test.ts test/regressions/fixtures/CssVarsProvider/MaterialUIDefaultDark.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-system/src/cssVars/prepareCssVars.ts->program->function_declaration:prepareCssVars"] |
mui/material-ui | 36,890 | mui__material-ui-36890 | ['36889'] | ea0228b35d7eed4f9c120b1dd4aac64756c6a039 | diff --git a/packages/mui-material/src/MenuList/MenuList.js b/packages/mui-material/src/MenuList/MenuList.js
--- a/packages/mui-material/src/MenuList/MenuList.js
+++ b/packages/mui-material/src/MenuList/MenuList.js
@@ -211,6 +211,13 @@ const MenuList = React.forwardRef(function MenuList(props, ref) {
// item and use... | diff --git a/packages/mui-material/src/Select/Select.test.js b/packages/mui-material/src/Select/Select.test.js
--- a/packages/mui-material/src/Select/Select.test.js
+++ b/packages/mui-material/src/Select/Select.test.js
@@ -563,6 +563,62 @@ describe('<Select />', () => {
expect(options[5]).to.have.attribute('... | TypeError using conditional rendering under ListSubheader
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/friendly-zhukovsky-i08cjd?file=/demo.js
Steps:
1. ListSubheader... | null | 2023-04-14 22:26:51+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Select/Select.test.js-><Select /> prop: onChange should not be called if selected element has the current value (value did not change)', 'packages/mui-material/src/Select/Select.test.js-><Select /> accessibility when the first child is a ListSubheader wrapped in a custom component with the `... | ['packages/mui-material/src/Select/Select.test.js-><Select /> accessibility when the first child is a ListSubheader when the second child is conditionally rendering with "" first selectable option is focused to use the arrow', 'packages/mui-material/src/Select/Select.test.js-><Select /> accessibility when the first chi... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Select/Select.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 36,971 | mui__material-ui-36971 | ['33423'] | be6b6e2bc479473853ea2ecd367cd1a46c728ad9 | diff --git a/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js b/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js
new file mode 100644
--- /dev/null
+++ b/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js
@@ -0,0 +1,631 @@
+import * as React from 'react... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -3026,6 +3026,27 @@ describe('<Autocomplete />', (... | [Autocomplete] Pass `getOptionLabel` as a parameter to `renderOption`
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
The `renderOption` callback of the `Autocomplete` component could receive the components getOptionLabel callback a ... | I think we can go ahead with adding the `ownerState` as a fourth parameter to `renderOption`.
Would you like to create a PR for it?
@ZeeshanTamboli I can try, but it will take some time.
> @ZeeshanTamboli I can try, but it will take some time.
No problem at all!
@ZeeshanTamboli Do you mind me asking if you are w... | 2023-04-23 13:17:19+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: renderOption should pass getOptionLabel through ownerState in renderOption callback'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 37,118 | mui__material-ui-37118 | ['36283'] | 5b6e6c5ccf19ffbf251cd19ead587774f17f6ec0 | diff --git a/docs/data/base/components/select/UnstyledSelectIntroduction.js b/docs/data/base/components/select/UnstyledSelectIntroduction.js
--- a/docs/data/base/components/select/UnstyledSelectIntroduction.js
+++ b/docs/data/base/components/select/UnstyledSelectIntroduction.js
@@ -83,6 +83,7 @@ Button.propTypes = {
... | diff --git a/packages/mui-base/src/useList/listReducer.test.ts b/packages/mui-base/src/useList/listReducer.test.ts
--- a/packages/mui-base/src/useList/listReducer.test.ts
+++ b/packages/mui-base/src/useList/listReducer.test.ts
@@ -22,7 +22,7 @@ describe('listReducer', () => {
focusManagement: 'activeDescenda... | [Select][base] Consistency in props naming
Decide on the naming convention of functional props in SelectUnstyled. Currently, they are named inconsistently: `getSerializedValue`, `optionStringifier`, `renderValue`.
The possible options include:
1. A noun: `valueSerializer`, `optionStringifier`, `valueRenderer`.
2... | > 3. A noun with a "get" prefix: getSerializedValue, getStringifiedOption, getRenderedValue
This feels most intuitive for me. This is the pattern we use in other components too, for e.g. the Material UI's Autocomplete.
Thanks for your opinion. For me, either option 1 or 3 sounds best. Option 2 kind of suggests it's ... | 2023-05-01 12:05:18+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/useSelect/selectReducer.test.ts->selectReducer action: buttonClick highlights the first value if the select was closed and nothing was selected', 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: keyDown Enter key is pressed replaces the selectedValues with the highlighted ... | ['packages/mui-base/src/useList/listReducer.test.ts->listReducer action: textNavigation should highlight first match that is not disabled', 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: textNavigation should move highlight to disabled items if disabledItemsFocusable=true', 'packages/mui-base/s... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/useSelect/selectReducer.test.ts packages/mui-base/src/useList/listReducer.test.ts --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/mui-base/src/useMenu/useMenu.ts->program->function_declaration:useMenu", "packages/mui-base/src/useList/listReducer.ts->program->function_declaration:handleTextNavigation", "packages/mui-base/src/useList/useList.ts->program->function_declaration:useList", "packages/mui-base/src/useSelect/useSelect.ts->progra... |
mui/material-ui | 37,141 | mui__material-ui-37141 | ['36783'] | 9710ff34b16a0f271107a8619a28546ae3ca7c18 | diff --git a/packages/mui-base/src/useSelect/useSelect.ts b/packages/mui-base/src/useSelect/useSelect.ts
--- a/packages/mui-base/src/useSelect/useSelect.ts
+++ b/packages/mui-base/src/useSelect/useSelect.ts
@@ -64,14 +64,20 @@ function useSelect<OptionValue, Multiple extends boolean = false>(
if (valueProp === undef... | diff --git a/packages/mui-base/src/Select/Select.test.tsx b/packages/mui-base/src/Select/Select.test.tsx
--- a/packages/mui-base/src/Select/Select.test.tsx
+++ b/packages/mui-base/src/Select/Select.test.tsx
@@ -665,7 +665,7 @@ describe('<Select />', () => {
expect(handleChange.args[0][1]).to.equal(2);
});
... | [Joy][Select] onChange callback fires without user interaction
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/select-onchange-callback-mb1n7d?file=/demo.tsx
S... | I agree with @sibljon so mark this as a bug. I think this might related to Base UI than Joy UI. @michaldudak Would the latest refactor of the Listbox fixes this?
Yes, this issue should be fixed on master (it will be released on Monday or Tuesday).
@michaldudak I'm currently using the latest version (`5.0.0-alpha.127`) ... | 2023-05-02 19:11:04+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is called after initial render with `null` when the controlled value is set to a nonexistent option', "packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the root slot's element with a ca... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is not called after initial render when when the default uncontrolled value is set to null', 'packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is not called after initial render when when controlled value is set to null'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Select/Select.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:useSelect"] |
mui/material-ui | 37,392 | mui__material-ui-37392 | ['36800'] | 5e2d83c9d4c25fb6d4aa326fcc95ae2c00de52c8 | diff --git a/docs/pages/base-ui/api/menu.json b/docs/pages/base-ui/api/menu.json
--- a/docs/pages/base-ui/api/menu.json
+++ b/docs/pages/base-ui/api/menu.json
@@ -7,6 +7,7 @@
"description": "HTML element<br>| object<br>| func"
}
},
+ "onItemsChange": { "type": { "name": "func... | diff --git a/packages/mui-base/src/Menu/Menu.test.tsx b/packages/mui-base/src/Menu/Menu.test.tsx
--- a/packages/mui-base/src/Menu/Menu.test.tsx
+++ b/packages/mui-base/src/Menu/Menu.test.tsx
@@ -358,4 +358,26 @@ describe('<Menu />', () => {
});
});
});
+
+ describe('prop: onItemsChange', () => {
+ it... | [joy][base][Menu] MenuItem `tabindex` isn't logical in a changing list
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/modest-gates-zwyhbd?file=/demo.tsx
This is the same e... | I will check this issue
Agreed with the bug, i can reproduce
1. 'Menuitem' elements run registerItem() when mounted and unregisterItem() when unmounted.(useMenuItem.ts)
2. registerItem() and unregisterItem() run setMenuItems() to add and delete the data of the element to the 'menuitems' variable. (useMenu.ts)
Where... | 2023-05-24 14:12:27+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ["packages/mui-base/src/Menu/Menu.test.tsx-><Menu /> MUI unstyled component API sets the ownerState prop on the root slot's component", 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: keyDown Enter key is pressed replaces the selectedValues with the highlighted value if selectionMode = "single"'... | ['packages/mui-base/src/Menu/Menu.test.tsx-><Menu /> prop: onItemsChange should be called when the menu items change', 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: resetHighlight highlights the first non-disabled item', 'packages/mui-base/src/useList/listReducer.test.ts->listReducer action: r... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Menu/Menu.test.tsx packages/mui-base/src/useList/listReducer.test.ts --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/mui-base/src/useMenu/useMenu.ts->program->function_declaration:useMenu", "packages/mui-base/src/useList/listReducer.ts->program->function_declaration:handleResetHighlight", "packages/mui-base/src/useList/listReducer.ts->program->function_declaration:listReducer", "packages/mui-base/src/useList/useList.ts->pr... |
mui/material-ui | 37,465 | mui__material-ui-37465 | ['36416'] | bf1a4fc8f9fba7dad9657ce6db1d5500b8aaf4cf | diff --git a/docs/data/material/components/popover/VirtualElementPopover.js b/docs/data/material/components/popover/VirtualElementPopover.js
new file mode 100644
--- /dev/null
+++ b/docs/data/material/components/popover/VirtualElementPopover.js
@@ -0,0 +1,58 @@
+import * as React from 'react';
+import Popover from '@mu... | diff --git a/packages/mui-material/src/Popover/Popover.test.js b/packages/mui-material/src/Popover/Popover.test.js
--- a/packages/mui-material/src/Popover/Popover.test.js
+++ b/packages/mui-material/src/Popover/Popover.test.js
@@ -448,6 +448,38 @@ describe('<Popover />', () => {
);
expect(anchorElSpy.call... | [Material][Popover] Can it support VirtualElement like `Popper?
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
Popper component inherits the feature of using a `VirtualElement` as it's `anchorEl`, it provides a convenient way to set... | The request makes sense to me 👍 It is documented on both popper and Floating UI's documentation (we are likely to migrate to it in the future). Here are the benchmarks:
- https://popper.js.org/react-popper/v2/virtual-elements/
- https://floating-ui.com/docs/virtual-elements
We can add a demo for it, as I don't ... | 2023-06-01 15:23:10+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Popover/Popover.test.js-><Popover /> positioning on an anchor should be positioned over the bottom left of the anchor', 'packages/mui-material/src/Popover/Popover.test.js-><Popover /> positioning when `marginThreshold=18` bottom > heightThreshold test', 'packages/mui-material/src/Popover/Pop... | ['packages/mui-material/src/Popover/Popover.test.js-><Popover /> warnings should warn if anchorEl is not valid'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Popover/Popover.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 37,530 | mui__material-ui-37530 | ['18119'] | 7aa3fab10217d0a4c4ac2bd82d0ef5b80d6b18e9 | diff --git a/packages/mui-material/src/Tooltip/Tooltip.js b/packages/mui-material/src/Tooltip/Tooltip.js
--- a/packages/mui-material/src/Tooltip/Tooltip.js
+++ b/packages/mui-material/src/Tooltip/Tooltip.js
@@ -233,7 +233,7 @@ const Tooltip = React.forwardRef(function Tooltip(inProps, ref) {
const props = useThemePr... | diff --git a/packages/mui-material/src/Tooltip/Tooltip.test.js b/packages/mui-material/src/Tooltip/Tooltip.test.js
--- a/packages/mui-material/src/Tooltip/Tooltip.test.js
+++ b/packages/mui-material/src/Tooltip/Tooltip.test.js
@@ -994,6 +994,12 @@ describe('<Tooltip />', () => {
'The `children` component of th... | [Tooltip] TypeError: Cannot read property 'className' of undefined
I am getting this error. Code is crashing.
https://codesandbox.io/s/basictooltip-material-demo-forked-7ftwd
<img width="1010" alt="Screenshot 2019-10-31 at 17 50 39" src="https://user-images.githubusercontent.com/2432618/67948413-79350800-fc07-11e... | Check the documentation, the Tooltip requires an element as a child that forward the ref, for instance:
```jsx
<Tooltip title="Foo">
<span>Bar</span>
</Tooltip>
```
Maybe that could be the error message if there is no child element present.
> Maybe that could be the error message if there is no child element p... | 2023-06-06 20:40:12+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: title should label the child when open with an exotic title', 'packages/mui-material/src/Tooltip/Tooltip.test.js-><Tooltip /> MUI component API allows overriding the transition slot with a component using the components.Transition prop', 'packages/m... | ['packages/mui-material/src/Tooltip/Tooltip.test.js-><Tooltip /> warnings should warn when children is a string'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 37,615 | mui__material-ui-37615 | ['37597'] | b97b3345e81931d588e5cf54e9a7ea6b4315c9df | diff --git a/docs/pages/base-ui/api/select.json b/docs/pages/base-ui/api/select.json
--- a/docs/pages/base-ui/api/select.json
+++ b/docs/pages/base-ui/api/select.json
@@ -1,5 +1,6 @@
{
"props": {
+ "areOptionsEqual": { "type": { "name": "func" } },
"autoFocus": { "type": { "name": "bool" }, "default": "fals... | diff --git a/packages/mui-base/src/Select/Select.test.tsx b/packages/mui-base/src/Select/Select.test.tsx
--- a/packages/mui-base/src/Select/Select.test.tsx
+++ b/packages/mui-base/src/Select/Select.test.tsx
@@ -851,6 +851,24 @@ describe('<Select />', () => {
});
});
+ describe('prop: areOptionsEqual', () => ... | [Select] onChange fired on init when passing initial values
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/hopeful-visvesvaraya-r527yc?file=/demo.tsx
Linked with [36783](... | null | 2023-06-16 19:57:12+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is called after initial render with `null` when the controlled value is set to a nonexistent option', "packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the root slot's element with a ca... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: areOptionsEqual should use the `areOptionsEqual` prop to determine if an option is selected'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Select/Select.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/mui-base/src/utils/useControllableReducer.ts->program->function_declaration:useStateChangeDetection", "packages/mui-base/src/utils/useControllableReducer.ts->program->function_declaration:useControllableReducer", "packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:useSelect"] |
mui/material-ui | 37,692 | mui__material-ui-37692 | ['37687'] | 1af04d2aa1dd2356a24c7f31d7a2f7a174ba3cbb | diff --git a/packages/mui-joy/src/ButtonGroup/ButtonGroup.tsx b/packages/mui-joy/src/ButtonGroup/ButtonGroup.tsx
--- a/packages/mui-joy/src/ButtonGroup/ButtonGroup.tsx
+++ b/packages/mui-joy/src/ButtonGroup/ButtonGroup.tsx
@@ -46,6 +46,7 @@ const ButtonGroupRoot = styled('div', {
ownerState.orientation === 'vertic... | diff --git a/packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx b/packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx
--- a/packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx
+++ b/packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx
@@ -174,6 +174,16 @@ describe('<ButtonGroup />', () => {
expect(containe... | [Joy][ButtonGroup] Single button in a button group doesn't properly round corners
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/exciting-black-y2glhj
Steps:
... | I have added a second scenario to this report where if a Button is imported as a component, the border radius is missing entirely. | 2023-06-24 13:50:47+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx-><ButtonGroup /> prop: color should render danger', 'packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx-><ButtonGroup /> prop: color should override button group value', 'packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx-><ButtonGroup /> MUI component API s... | ['packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx-><ButtonGroup /> should not add data-attribute to single child'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/ButtonGroup/ButtonGroup.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 37,773 | mui__material-ui-37773 | ['37752'] | b0abb28940667235e278f19376e44244971cd420 | diff --git a/docs/pages/material-ui/api/popover.json b/docs/pages/material-ui/api/popover.json
--- a/docs/pages/material-ui/api/popover.json
+++ b/docs/pages/material-ui/api/popover.json
@@ -23,6 +23,7 @@
"children": { "type": { "name": "node" } },
"classes": { "type": { "name": "object" }, "additionalInfo": ... | diff --git a/packages/mui-material/src/Popover/Popover.test.js b/packages/mui-material/src/Popover/Popover.test.js
--- a/packages/mui-material/src/Popover/Popover.test.js
+++ b/packages/mui-material/src/Popover/Popover.test.js
@@ -844,8 +844,8 @@ describe('<Popover />', () => {
});
});
- [0, 18, 16].forEach(... | TextField component's with select option and disableScrollLock menu stays fixed when scrolling
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/bitter-violet-wpfhc4?file=/src/A... | Thanks, it looks like a bug. Would you like to contribute to the project by investigating it?
> Thanks, it looks like a bug. Would you like to contribute to the project by investigating it?
I am afraid I don't have possibility to look into it anytime soon.
I'm open to taking a look at this.
To confirm, the expe... | 2023-07-01 22:20:50+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Popover/Popover.test.js-><Popover /> positioning on an anchor should be positioned over the bottom left of the anchor', 'packages/mui-material/src/Popover/Popover.test.js-><Popover /> prop: marginThreshold positioning when `marginThreshold=0` bottom > heightThreshold test', 'packages/mui-mat... | ['packages/mui-material/src/Popover/Popover.test.js-><Popover /> prop: marginThreshold positioning when `marginThreshold=null` should not apply the marginThreshold when marginThreshold is null'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Popover/Popover.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 37,845 | mui__material-ui-37845 | ['37000'] | ab2cb8cf9614ccab02b62a22de5129a1c2774d96 | diff --git a/packages/mui-joy/src/styles/extendTheme.ts b/packages/mui-joy/src/styles/extendTheme.ts
--- a/packages/mui-joy/src/styles/extendTheme.ts
+++ b/packages/mui-joy/src/styles/extendTheme.ts
@@ -379,8 +379,8 @@ export default function extendTheme(themeOptions?: CssVarsThemeOptions): Theme {
const fontFamilyF... | diff --git a/packages/mui-joy/src/styles/extendTheme.test.js b/packages/mui-joy/src/styles/extendTheme.test.js
--- a/packages/mui-joy/src/styles/extendTheme.test.js
+++ b/packages/mui-joy/src/styles/extendTheme.test.js
@@ -92,6 +92,16 @@ describe('extendTheme', () => {
});
});
+ it('should have correct font ... | [Joy] Using extendTheme with fontFamily can lead to invalid CSS variable names
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
From https://gitlab.com/sagotch/teztale-dataviz/ (and more precisely this merge request: https:... | Looks like a bug to me. | 2023-07-06 12:54:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/cssVars/createGetCssVar.test.ts->createGetCssVar default without prefix should return correct CSS var with comma', 'packages/mui-system/src/cssVars/createGetCssVar.test.ts->createGetCssVar does not add var() to CSS value', 'packages/mui-joy/src/styles/extendTheme.test.js->extendTheme theme.uns... | ['packages/mui-joy/src/styles/extendTheme.test.js->extendTheme should have correct font family'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/styles/extendTheme.test.js packages/mui-system/src/cssVars/createGetCssVar.test.ts --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-joy/src/styles/extendTheme.ts->program->function_declaration:extendTheme"] |
mui/material-ui | 37,855 | mui__material-ui-37855 | ['37673'] | b00bdc767032fd008e5e3ec3133d6dc51264b1de | diff --git a/packages/mui-base/src/useSelect/useSelect.ts b/packages/mui-base/src/useSelect/useSelect.ts
--- a/packages/mui-base/src/useSelect/useSelect.ts
+++ b/packages/mui-base/src/useSelect/useSelect.ts
@@ -255,10 +255,10 @@ function useSelect<OptionValue, Multiple extends boolean = false>(
rootRef: mergedList... | diff --git a/packages/mui-base/src/Select/Select.test.tsx b/packages/mui-base/src/Select/Select.test.tsx
--- a/packages/mui-base/src/Select/Select.test.tsx
+++ b/packages/mui-base/src/Select/Select.test.tsx
@@ -77,7 +77,7 @@ describe('<Select />', () => {
const select = getByRole('combobox');
act(() =... | [Select][base] In controlled mode, the button flashes when clicked
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/magical-banach-v4s39j?file=/demo.js
Steps:
1. Click on ... | Thanks for reporting it. We'll look into it soon.
I'm available to look into this. | 2023-07-07 02:07:46+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ["packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the root slot's element with a callback function", "packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the listbox slot's element", 'packages/mui-joy... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> keyboard navigation item selection selects a highlighted item using the "Enter" key', 'packages/mui-base/src/Select/Select.test.tsx-><Select /> open/close behavior opens the listbox when the select is clicked', 'packages/mui-base/src/Select/Select.test.tsx-><Se... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/Select/Select.test.tsx packages/mui-base/src/Select/Select.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:useSelect"] |
mui/material-ui | 37,908 | mui__material-ui-37908 | ['32967'] | 8db6cf291c07117b75173fbf2218bf530dfd78e3 | diff --git a/docs/data/joy/guides/themeable-component/StatComponent.js b/docs/data/joy/guides/themeable-component/StatComponent.js
new file mode 100644
--- /dev/null
+++ b/docs/data/joy/guides/themeable-component/StatComponent.js
@@ -0,0 +1,30 @@
+import * as React from 'react';
+import { styled } from '@mui/joy/styles... | diff --git a/packages/mui-system/src/createStyled.test.js b/packages/mui-system/src/createStyled.test.js
--- a/packages/mui-system/src/createStyled.test.js
+++ b/packages/mui-system/src/createStyled.test.js
@@ -89,6 +89,42 @@ describe('createStyled', () => {
});
});
+ it('default overridesResolver', () => {
... | Give the possibility to create new Components using the Material theming system for unique behavior
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
Lets say I use material ui and want to create a generic component of some s... | Thanks for the feedback, you can import the `useThemeProps` hook from '@mui/material/styles`. We could add a bit of docs around it.
Actually, I really like the idea for adding guide for how to create custom components, that would behave and have all features common for all Material UI components. One potential issue... | 2023-07-11 06:55:18+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-system/src/createStyled.test.js->createStyled displayName falls back to the decorated tag name', 'packages/mui-system/src/createStyled.test.js->createStyled styleOverrides callback support template string return from the callback', 'packages/mui-system/src/createStyled.test.js->createStyled styleOverride... | ['packages/mui-system/src/createStyled.test.js->createStyled default overridesResolver'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/createStyled.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/mui-system/src/createStyled.js->program->function_declaration:createStyled", "packages/mui-system/src/createStyled.js->program->function_declaration:defaultOverridesResolver"] |
mui/material-ui | 38,100 | mui__material-ui-38100 | ['38048'] | 0f8eb07edbf21c585faf4803ab0122f23efbb2c7 | diff --git a/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js b/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js
--- a/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js
+++ b/docs/data/material/components/autocomplete/GloballyCustomizedOptions.js
@@ -2... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -3045,6 +3045,25 @@ describe('<Autocomplete />', (... | [Autocomplete] Access default `getOptionLabel` in `renderOption`
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
We are overriding the default `renderOption` but we cannot access `getOptionLabel` in the custom `renderOption` function... | Actually, `getOptionLabel` is passed in `ownerState` if a user passes a custom `getOptionLabel`. But the default `getOptionLabel` is not passed. So this seems more like a bug.
You are correct; there is a bug. We forgot to pass the default `getOptionLabel` prop to `ownerState` in #36971. All props with default values sh... | 2023-07-22 11:30:18+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: renderOption should pass getOptionLabel default value through ownerState when no custom getOptionLabel prop provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 38,167 | mui__material-ui-38167 | ['38070'] | e9b324c880892e9c6ebd2a627f0311478f50252b | diff --git a/docs/data/joy/components/input/InputFormProps.js b/docs/data/joy/components/input/InputFormProps.js
--- a/docs/data/joy/components/input/InputFormProps.js
+++ b/docs/data/joy/components/input/InputFormProps.js
@@ -8,6 +8,9 @@ export default function InputFormProps() {
<form
onSubmit={(event) =>... | diff --git a/packages/mui-base/src/Select/Select.test.tsx b/packages/mui-base/src/Select/Select.test.tsx
--- a/packages/mui-base/src/Select/Select.test.tsx
+++ b/packages/mui-base/src/Select/Select.test.tsx
@@ -523,7 +523,7 @@ describe('<Select />', () => {
const handleSubmit = (event: React.FormEvent<HTMLForm... | Joy UI Select should support "required" prop for native validation
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
Autocomplete, Input and Textarea all support "required" prop for native validation, but not Select. The feature exists... | @michaldudak @mj12albert Which approach do you recommend? I feel that we should start with how Base UI will support this first.
The ways I see it:
1. use `aria-required` on the Select button slot
2. use the existing hidden `input` and add `required` to it.
The first option, I think. I don't know if setting `requir... | 2023-07-26 12:40:52+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-base/src/Select/Select.test.tsx-><Select /> prop: onChange is called after initial render with `null` when the controlled value is set to a nonexistent option', "packages/mui-base/src/Select/Select.test.tsx-><Select /> MUI unstyled component API sets custom properties on the root slot's element with a ca... | ['packages/mui-base/src/useSelect/useSelect.test.tsx->useSelect getHiddenInputProps [multiple with object value] returns correct value for the hidden input', 'packages/mui-base/src/useSelect/useSelect.test.tsx->useSelect getHiddenInputProps returns props for hidden input', 'packages/mui-base/src/useSelect/useSelect.tes... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Select/Select.test.tsx packages/mui-base/src/useSelect/useSelect.test.tsx --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 4 | 0 | 4 | false | false | ["docs/data/joy/components/select/ControlledOpenSelect.js->program->function_declaration:ControlledOpenSelect", "packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:useSelect", "packages/mui-base/src/useSelect/useSelect.ts->program->function_declaration:defaultFormValueProvider", "docs/data/joy/... |
mui/material-ui | 38,182 | mui__material-ui-38182 | ['38176'] | d428acb95ca37028d9e5be4f87c13e0d1088fa42 | diff --git a/docs/pages/material-ui/api/checkbox.json b/docs/pages/material-ui/api/checkbox.json
--- a/docs/pages/material-ui/api/checkbox.json
+++ b/docs/pages/material-ui/api/checkbox.json
@@ -45,7 +45,16 @@
},
"name": "Checkbox",
"styles": {
- "classes": ["root", "checked", "disabled", "indeterminate", "... | diff --git a/packages/mui-material/src/Checkbox/Checkbox.test.js b/packages/mui-material/src/Checkbox/Checkbox.test.js
--- a/packages/mui-material/src/Checkbox/Checkbox.test.js
+++ b/packages/mui-material/src/Checkbox/Checkbox.test.js
@@ -66,6 +66,32 @@ describe('<Checkbox />', () => {
});
});
+ describe('pr... | [Checkbox][material] `size="small"` is not receiving any appropriate className to style off of
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Summary 💡
`<Checkbox size="small" />` should receive some className in the DOM (ie`.MuiCheckbox-size... | null | 2023-07-27 09:07:11+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-material/src/Checkbox/Checkbox.test.js-><Checkbox /> with FormControl disabled should have the disabled class', 'packages/mui-material/src/Checkbox/Checkbox.test.js-><Checkbox /> should allow custom icon font sizes', "packages/mui-material/src/Checkbox/Checkbox.test.js-><Checkbox /> MUI component API the... | ['packages/mui-material/src/Checkbox/Checkbox.test.js-><Checkbox /> prop: size add sizeMedium class to the root element when the size prop equals "medium"', 'packages/mui-material/src/Checkbox/Checkbox.test.js-><Checkbox /> prop: size add sizeSmall class to the root element when the size prop equals "small"', 'packages... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Checkbox/Checkbox.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 38,247 | mui__material-ui-38247 | ['37733'] | 85c3c776918e43c8034d0fbdb1a35ded54c6b92d | diff --git a/docs/src/modules/sandbox/CreateReactApp.ts b/docs/src/modules/sandbox/CreateReactApp.ts
--- a/docs/src/modules/sandbox/CreateReactApp.ts
+++ b/docs/src/modules/sandbox/CreateReactApp.ts
@@ -4,10 +4,12 @@ export const getHtml = ({
title,
language,
codeStyling,
+ raw,
}: {
title: string;
lan... | diff --git a/docs/src/modules/sandbox/CodeSandbox.test.js b/docs/src/modules/sandbox/CodeSandbox.test.js
--- a/docs/src/modules/sandbox/CodeSandbox.test.js
+++ b/docs/src/modules/sandbox/CodeSandbox.test.js
@@ -243,4 +243,23 @@ ReactDOM.createRoot(document.querySelector("#root")!).render(
'<script src="https://c... | [docs] The documentation for <Icon/> doesn't render an icon for the SandBox
### Duplicates
- [X] I have searched the existing issues
### Related page
https://mui.com/material-ui/icons/
### Kind of issue
Broken demonstration
### Issue description
cmd + f for "add_cicle"
and click on the codesandb... | The issue is that the `public/index.html` file in the sandbox is linking to the wrong icons.
Lines 10-14 of [the file](https://codesandbox.io/s/pwm967?file=/public/index.html:0-485) are:
```html
<!-- Icons to support Material Design -->
<link
rel="stylesheet"
href="https://fonts.googleapis.com/icon?family=M... | 2023-07-31 07:46:02+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['docs/src/modules/sandbox/StackBlitz.test.js->StackBlitz generate the correct index.html result when Tailwind is used', 'docs/src/modules/sandbox/CodeSandbox.test.js->CodeSandbox generate the correct JavaScript result', 'docs/src/modules/sandbox/CodeSandbox.test.js->CodeSandbox generate the correct index.html result w... | ['docs/src/modules/sandbox/CodeSandbox.test.js->CodeSandbox should generate the correct stylesheet font link in index.html for Material Two Tones icons', 'docs/src/modules/sandbox/StackBlitz.test.js->StackBlitz should generate the correct stylesheet font link in index.html for Material Two Tones icons'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha docs/src/modules/sandbox/CodeSandbox.test.js docs/src/modules/sandbox/StackBlitz.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 38,417 | mui__material-ui-38417 | ['38368'] | 6b99bc55253b21b856cd7a0df1888a3377525236 | diff --git a/packages/mui-base/src/useButton/useButton.ts b/packages/mui-base/src/useButton/useButton.ts
--- a/packages/mui-base/src/useButton/useButton.ts
+++ b/packages/mui-base/src/useButton/useButton.ts
@@ -187,6 +187,10 @@ export function useButton(parameters: UseButtonParameters = {}): UseButtonReturn
const ... | diff --git a/packages/mui-base/src/useButton/useButton.test.tsx b/packages/mui-base/src/useButton/useButton.test.tsx
--- a/packages/mui-base/src/useButton/useButton.test.tsx
+++ b/packages/mui-base/src/useButton/useButton.test.tsx
@@ -197,4 +197,46 @@ describe('useButton', () => {
});
});
});
+
+ descri... | [RFC][useButton][base] tabIndex should be returned by getRootProps if explicitly provided
### What's the problem? 🤔
The problem lies in [this section](https://github.com/mui/material-ui/blob/master/packages/mui-base/src/useButton/useButton.ts#L190-L206) of `useButton`'s implementation:
There are some conditions un... | null | 2023-08-10 19:58:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install --legacy-peer-deps
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format... | ['packages/mui-base/src/useButton/useButton.test.tsx->useButton state: active when using a button element is set when clicked on an element inside the button', 'packages/mui-base/src/useButton/useButton.test.tsx->useButton tabIndex returns tabIndex in getRootProps when host component is not BUTTON', 'packages/mui-base/... | ['packages/mui-base/src/useButton/useButton.test.tsx->useButton tabIndex returns tabIndex in getRootProps if it is explicitly provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/useButton/useButton.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useButton/useButton.ts->program->function_declaration:useButton"] |
mui/material-ui | 38,544 | mui__material-ui-38544 | ['38406'] | f22e9951931ecf68e8bce1c159d8e0384d92760c | diff --git a/packages/mui-material-next/src/Tabs/Tabs.js b/packages/mui-material-next/src/Tabs/Tabs.js
--- a/packages/mui-material-next/src/Tabs/Tabs.js
+++ b/packages/mui-material-next/src/Tabs/Tabs.js
@@ -146,10 +146,7 @@ const TabsIndicator = styled('span', {
}),
}));
-const TabsScrollbarSize = styled(Scrollba... | diff --git a/packages/mui-material/src/Tabs/Tabs.test.js b/packages/mui-material/src/Tabs/Tabs.test.js
--- a/packages/mui-material/src/Tabs/Tabs.test.js
+++ b/packages/mui-material/src/Tabs/Tabs.test.js
@@ -523,6 +523,37 @@ describe('<Tabs />', () => {
});
expect(tablistContainer.style.overflow).to.equal(... | [Tabs] Scrollable tabs crashes when overriding styles in theme using slots callback
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/mui-tabs-style-override-crash-p9w... | I ran into this as well, reading ownerState values in the theme styleOverrides for the Tabs component. Pinning `"@mui/material": "5.14.3"` and adding a resolution/override for `"@mui/system": "5.14.3"` is my temporary workaround.
I propose the fix like this:
```diff
diff --git a/packages/mui-material/src/Tabs/Tabs... | 2023-08-18 14:27:23+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons should not hide scroll buttons when allowScrollButtonsMobile is true', 'packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> MUI component API applies the className to the root component', 'packages/mui-material/src/Tabs/Tabs.test.js-><Tabs />... | ['packages/mui-material/src/Tabs/Tabs.test.js-><Tabs /> prop: variant="scrollable" should handle theme styleOverrides for scrollable tabs without crashing'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Tabs/Tabs.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 38,788 | mui__material-ui-38788 | ['39281'] | 5047813ad0927fc040eca65d484ef4d6a8c8e9ec | diff --git a/packages/mui-base/src/useAutocomplete/useAutocomplete.js b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
--- a/packages/mui-base/src/useAutocomplete/useAutocomplete.js
+++ b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
@@ -293,21 +293,13 @@ export function useAutocomplete(props) {
... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -823,6 +823,83 @@ describe('<Autocomplete />', () ... | [Autocomplete] Pressing ArrowDown key behaves incorrectly when remaining options are disabled
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/https-github-com-mui-ma... | null | 2023-09-03 13:00:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: getOptionDisabled should skip disabled options at the end of the list when navigating via keyboard', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: getOptionDisabled should skip the first and last... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete->function_declaration:validOptionIndex"] |
mui/material-ui | 39,071 | mui__material-ui-39071 | ['38478'] | ba4c5596cdbbdf07e78cb10ca7231db9968812db | diff --git a/packages/mui-system/src/style.js b/packages/mui-system/src/style.js
--- a/packages/mui-system/src/style.js
+++ b/packages/mui-system/src/style.js
@@ -35,6 +35,14 @@ export function getStyleValue(themeMapping, transform, propValueFinal, userValue
value = getPath(themeMapping, propValueFinal) || userVal... | diff --git a/packages/mui-material/src/Typography/Typography.test.js b/packages/mui-material/src/Typography/Typography.test.js
--- a/packages/mui-material/src/Typography/Typography.test.js
+++ b/packages/mui-material/src/Typography/Typography.test.js
@@ -112,6 +112,20 @@ describe('<Typography />', () => {
});
}... | [material] Invalid `color` prop has no effect
- [X] I have searched the existing issues
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: [CodeSandbox fork](https://codesandbox.io/s/mui-invalid-color-is-silently-swallowed-gtwdg2) based on the [Typography demo](https://mui.com... | Hey @o-alexandrov, thanks for the report!
This is a bug. I think what's happening is that "background" is a key in the [theme palette](https://mui.com/material-ui/customization/default-theme/?expand-path=$.palette), so we try to use that value, but it's an object (with `"paper"` and `"default"` keys). The expected b... | 2023-09-20 09:27:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Typography/Typography.test.js-><Typography /> MUI component API applies the root class to the root component if it has this class', 'packages/mui-material/src/Typography/Typography.test.js-><Typography /> should render body1 root by default', 'packages/mui-material/src/Typography/Typography.... | ['packages/mui-material/src/Typography/Typography.test.js-><Typography /> prop: color should check for invalid color value', 'packages/mui-system/src/style.test.js->style getStyleValue should warn on acceptable object', 'packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js->styleFunctionSx system resolves sy... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/style.test.js packages/mui-material/src/Typography/Typography.test.js packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js packages/mui-system/src/palette.test.js --reporter /testbed/custom-reporter.js --ex... | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-system/src/style.js->program->function_declaration:getStyleValue"] |
mui/material-ui | 39,297 | mui__material-ui-39297 | ['39284'] | 62d3b9669bbb1363ff7cf3009d9bfca8974c7b8f | diff --git a/docs/pages/base-ui/api/menu.json b/docs/pages/base-ui/api/menu.json
--- a/docs/pages/base-ui/api/menu.json
+++ b/docs/pages/base-ui/api/menu.json
@@ -1,6 +1,12 @@
{
"props": {
"actions": { "type": { "name": "custom", "description": "ref" } },
+ "anchor": {
+ "type": {
+ "name": "uni... | diff --git a/packages/mui-base/src/Menu/Menu.test.tsx b/packages/mui-base/src/Menu/Menu.test.tsx
--- a/packages/mui-base/src/Menu/Menu.test.tsx
+++ b/packages/mui-base/src/Menu/Menu.test.tsx
@@ -409,4 +409,68 @@ describe('<Menu />', () => {
expect(handleItemsChange.callCount).to.equal(2);
});
});
+
+ de... | [Menu][base-ui] Add the `anchor` prop to the Menu
As discussed in the comments of https://github.com/mui/material-ui/issues/38324, there's a need to directly provide the anchor element to the menu, so it can be anchored to an element that didn't trigger it.
| null | 2023-10-03 20:59:15+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-base/src/Menu/Menu.test.tsx-><Menu /> MUI unstyled component API does forward standard props to the root element if an intrinsic element is provided', "packages/mui-base/src/Menu/Menu.test.tsx-><Menu /> MUI unstyled component API sets the ownerState prop on the root slot's component", 'packages/mui-base/... | ['packages/mui-base/src/Menu/Menu.test.tsx-><Menu /> prop: anchor should be placed near the specified element', 'packages/mui-base/src/Menu/Menu.test.tsx-><Menu /> prop: anchor should be placed at the specified position'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-base/src/Menu/Menu.test.tsx --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 39,353 | mui__material-ui-39353 | ['39336'] | f69997e32614d07f26782dddd0fb6f96c67c3c4d | diff --git a/docs/pages/material-ui/api/table-pagination.json b/docs/pages/material-ui/api/table-pagination.json
--- a/docs/pages/material-ui/api/table-pagination.json
+++ b/docs/pages/material-ui/api/table-pagination.json
@@ -12,9 +12,14 @@
"page": { "type": { "name": "custom", "description": "integer" }, "requir... | diff --git a/packages/mui-material/src/TablePagination/TablePagination.test.js b/packages/mui-material/src/TablePagination/TablePagination.test.js
--- a/packages/mui-material/src/TablePagination/TablePagination.test.js
+++ b/packages/mui-material/src/TablePagination/TablePagination.test.js
@@ -353,6 +353,112 @@ describ... | [material-ui][TablePagination] Ability to show, but disable, the first/last page buttons
### Summary 💡
When paging through results and waiting on the API to return the next set of results, we like to disable the pagination controls. It's possible to do this for the page size dropdown, previous page button, and last p... | Since the grid uses the [`TablePagination`](https://mui.com/material-ui/react-pagination/#table-pagination) component from the core for this part of the application, I think allowing this enhancement there is better.
I'll transfer the issue there for the team to have a look.
CC @mui/core team | 2023-10-08 23:18:49+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: labelRowsPerPage labels the select for the current page', 'packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: showLastButton should change the page', 'packages/mui-material/src/TableP... | ['packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: slotProps actions previousButton should override backIconButtonProps', 'packages/mui-material/src/TablePagination/TablePagination.test.js-><TablePagination /> prop: disabled should disable the first, last, next, and back butt... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/TablePagination/TablePagination.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 39,536 | mui__material-ui-39536 | ['39535'] | c577e38f0711a6105e8b819c4549963a77e4ef08 | diff --git a/docs/pages/material-ui/api/toggle-button-group.json b/docs/pages/material-ui/api/toggle-button-group.json
--- a/docs/pages/material-ui/api/toggle-button-group.json
+++ b/docs/pages/material-ui/api/toggle-button-group.json
@@ -45,7 +45,15 @@
"import { ToggleButtonGroup } from '@mui/material';"
],
... | diff --git a/packages/mui-material/src/ButtonGroup/ButtonGroup.test.js b/packages/mui-material/src/ButtonGroup/ButtonGroup.test.js
--- a/packages/mui-material/src/ButtonGroup/ButtonGroup.test.js
+++ b/packages/mui-material/src/ButtonGroup/ButtonGroup.test.js
@@ -136,7 +136,7 @@ describe('<ButtonGroup />', () => {
... | [material-ui][ToggleButton] Can't customize it with `fullWidth`
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
```ts
MuiToggleButton: {
styleOverrides: {
fullwidth: { // TS ERROR: ... 'fullWid... | null | 2023-10-20 16:05:00+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/ButtonGroup/ButtonGroup.test.js-><ButtonGroup /> can pass fullWidth to Button', 'packages/mui-material/src/ButtonGroup/ButtonGroup.test.js-><ButtonGroup /> MUI component API applies the className to the root component', 'packages/mui-material/src/ButtonGroup/ButtonGroup.test.js-><ButtonGroup... | ['packages/mui-material/src/ToggleButtonGroup/ToggleButtonGroup.test.js-><ToggleButtonGroup /> can pass fullWidth to Button'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/ToggleButtonGroup/ToggleButtonGroup.test.js packages/mui-material/src/ButtonGroup/ButtonGroup.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 39,679 | mui__material-ui-39679 | ['34415'] | b6f2e488d639e42d4e2d0518a0fecc4df5167c18 | diff --git a/docs/data/material/components/button-group/LoadingButtonGroup.js b/docs/data/material/components/button-group/LoadingButtonGroup.js
new file mode 100644
--- /dev/null
+++ b/docs/data/material/components/button-group/LoadingButtonGroup.js
@@ -0,0 +1,17 @@
+import * as React from 'react';
+import ButtonGroup... | diff --git a/packages/mui-lab/src/LoadingButton/LoadingButton.test.js b/packages/mui-lab/src/LoadingButton/LoadingButton.test.js
--- a/packages/mui-lab/src/LoadingButton/LoadingButton.test.js
+++ b/packages/mui-lab/src/LoadingButton/LoadingButton.test.js
@@ -1,8 +1,9 @@
import * as React from 'react';
import { create... | LoadingButton doesn't inherit from ButtonGroup props
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Steps
1. Adding a LoadingButton component as a child of a ButtonGroup
2. Set variant, size or color prop on the Butto... | The `LoadingButton` does not use the context from the `ButtonGroup` so I mark this as a new feature.
**Off topic** I am also wondering if having a `LoadingButton` instead of `<Button loading />` is the right way to go.
I think so, to solve this issue we did it this way for the moment.
There is less utilities than t... | 2023-10-30 18:57:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-lab/src/LoadingButton/LoadingButton.test.js-><LoadingButton /> prop: loadingIndicator is not rendered by default', 'packages/mui-lab/src/LoadingButton/LoadingButton.test.js-><LoadingButton /> ButtonGroup works with LoadingButton correctly applies position classes to loading buttons', 'packages/mui-lab/sr... | ['packages/mui-lab/src/LoadingButton/LoadingButton.test.js-><LoadingButton /> ButtonGroup works with LoadingButton correctly passes props to children'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-lab/src/LoadingButton/LoadingButton.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 39,775 | mui__material-ui-39775 | ['26380'] | 6b9cee5d523304e0a8f3c8fd93a380d27be1df76 | diff --git a/packages/mui-material/src/Rating/Rating.js b/packages/mui-material/src/Rating/Rating.js
--- a/packages/mui-material/src/Rating/Rating.js
+++ b/packages/mui-material/src/Rating/Rating.js
@@ -367,14 +367,14 @@ const Rating = React.forwardRef(function Rating(inProps, ref) {
}
const rootNode = root... | diff --git a/packages/mui-material/src/Rating/Rating.test.js b/packages/mui-material/src/Rating/Rating.test.js
--- a/packages/mui-material/src/Rating/Rating.test.js
+++ b/packages/mui-material/src/Rating/Rating.test.js
@@ -46,18 +46,62 @@ describe('<Rating />', () => {
stub(container.firstChild, 'getBoundingClient... | Can't get correct position after changing spacing of icons in <Rating /> component in v5.
For some reasons, I need to change the spacing between icons in `<Rating />` component, but it causes the component cannot get correct position of each icons.
Here is the demo:
https://codesandbox.io/s/halfrating-material-d... | We have same problems. Increasing the margin between rating icons (adding padding/margin to the elements, or stretching the component using display: flex) causes same issues.
@eps1lon any update on the issue? Thanks.
Using `sx={{ width: '100%', justifyContent: 'space-between' }}` to try to make the icons evenly spaced ... | 2023-11-06 13:17:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-material/src/Rating/Rating.test.js-><Rating /> MUI component API applies the root class to the root component if it has this class', 'packages/mui-material/src/Rating/Rating.test.js-><Rating /> MUI component API ref attaches the ref', 'packages/mui-material/src/Rating/Rating.test.js-><Rating /> should se... | ['packages/mui-material/src/Rating/Rating.test.js-><Rating /> should handle mouse hover correctly for icons with spacing', 'packages/mui-material/src/Rating/Rating.test.js-><Rating /> should handle mouse hover correctly'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-material/src/Rating/Rating.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 39,962 | mui__material-ui-39962 | ['33335'] | 553cf822f6500075d374f3e89ad04b8308cd9f47 | diff --git a/packages/mui-system/src/borders.js b/packages/mui-system/src/borders.js
--- a/packages/mui-system/src/borders.js
+++ b/packages/mui-system/src/borders.js
@@ -12,60 +12,37 @@ export function borderTransform(value) {
return `${value}px solid`;
}
-export const border = style({
- prop: 'border',
- them... | diff --git a/packages/mui-system/src/borders.test.js b/packages/mui-system/src/borders.test.js
--- a/packages/mui-system/src/borders.test.js
+++ b/packages/mui-system/src/borders.test.js
@@ -4,10 +4,14 @@ import borders from './borders';
describe('borders', () => {
it('should work', () => {
const output = bord... | [system] `sx` field outlineColor doesn't take the theme into account
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Current behavior 😯
Using `background.action` for the sx field `outlineColor` does not update to the correct color in... | `outlineColor` cannot receive a string representing the `theme.palette` path. There are only few properties like `bgcolor`, `backgroundColor`, `color` that support it.
You can use a callback function to access theme.
```jsx
<Box sx={{ outlineColor: (theme) => theme.palette.action.active }}>
Hello World
</Box... | 2023-11-22 11:44:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ['packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js->styleFunctionSx `sx` of function type resolves system padding', 'packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js->styleFunctionSx theme callback works on nested selectors', 'packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js... | ['packages/mui-system/src/borders.test.js->borders should work', 'packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js->styleFunctionSx system resolves system '] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-system/src/borders.test.js packages/mui-system/src/styleFunctionSx/styleFunctionSx.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-system/src/borders.js->program->function_declaration:createBorderStyle"] |
mui/material-ui | 40,180 | mui__material-ui-40180 | ['40112'] | 33f16fb66f22f99ea6cba9e4b6bc26fd85335390 | diff --git a/packages/mui-joy/src/FormLabel/FormLabel.tsx b/packages/mui-joy/src/FormLabel/FormLabel.tsx
--- a/packages/mui-joy/src/FormLabel/FormLabel.tsx
+++ b/packages/mui-joy/src/FormLabel/FormLabel.tsx
@@ -62,7 +62,16 @@ const FormLabel = React.forwardRef(function FormLabel(inProps, ref) {
name: 'JoyFormLabel... | diff --git a/packages/mui-joy/src/FormControl/FormControl.test.tsx b/packages/mui-joy/src/FormControl/FormControl.test.tsx
--- a/packages/mui-joy/src/FormControl/FormControl.test.tsx
+++ b/packages/mui-joy/src/FormControl/FormControl.test.tsx
@@ -505,4 +505,22 @@ describe('<FormControl />', () => {
expect(getByR... | [joy-ui][FormLabel] `htmlFor` attribute not working as expected (disappears when set to undefined)
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### Steps to reproduce 🕹
Link to live example: https://codesandbox.io/p/sandbox/epic-turin... | I just realized that exactly the same behaviour can be observed with the `id` attribute (setting it to undefined overrides the default behaviour and removes it completely).
I can confirm it's a bug and appears to be easily fixable. Are you interested in creating a pull request? | 2023-12-11 23:13:31+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && npm install --legacy-peer-deps && npm install -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util --legacy-peer-dep... | ["packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> MUI component API theme default components: respect theme's defaultProps", 'packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> Input should linked the label', 'packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl... | ['packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> should inherit id from FormControl if id is undefined', 'packages/mui-joy/src/FormControl/FormControl.test.tsx-><FormControl /> should inherit htmlFor from FormControl if htmlFor is undefined'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && npx cross-env NODE_ENV=test mocha packages/mui-joy/src/FormControl/FormControl.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 41,300 | mui__material-ui-41300 | ['40843'] | 0faf15dabc34e83939ac8016b6b24454c8db11a2 | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.js b/packages/mui-material/src/Autocomplete/Autocomplete.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.js
@@ -582,6 +582,76 @@ const Autocomplete = React.forwardRef(function Autoc... | diff --git a/packages/mui-material/src/Autocomplete/Autocomplete.test.js b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
--- a/packages/mui-material/src/Autocomplete/Autocomplete.test.js
+++ b/packages/mui-material/src/Autocomplete/Autocomplete.test.js
@@ -2336,6 +2336,22 @@ describe('<Autocomplete />', (... | [material-ui][Autocomplete] The options list is added to the DOM even when there are no options, causing style problems
### Search keywords
Autocomplete, freeSolo, empty-options-list
### Latest version
- [X] I have tested the latest version
### Steps to reproduce
Link to live example: (required)
https:/... | I would like to work on this issue. Please let me know.
Seems like a bug. The Popper appears in the DOM even when there are no options in free solo mode. This might have been done to handle the loading state with the `loading` prop when options are still being fetched and also when we want to show "no options" when it ... | 2024-02-28 04:56:53+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:18
WORKDIR /testbed
COPY package.json pnpm-lock.yaml ./
RUN npm install -g pnpm@9.4.0
RUN npx playwright install --with-deps
RUN pnpm install
COPY . .
RUN pnpm add -w -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @typ... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input when `openOnFocus` toggles if empty', 'packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> highlight synchronisation should not update the highlight when multiple open and value change', 'packages/mui-m... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: freeSolo should not render popper when there are no options'] | ['packages/pigment-react/tests/pigment.test.ts->zero-runtime test input file styled.input.js'] | pnpm cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 41,306 | mui__material-ui-41306 | ['41386'] | 16e8ef70c0cc9553cc869ad8504440591e7c95e7 | diff --git a/packages/mui-base/src/useAutocomplete/useAutocomplete.js b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
--- a/packages/mui-base/src/useAutocomplete/useAutocomplete.js
+++ b/packages/mui-base/src/useAutocomplete/useAutocomplete.js
@@ -478,7 +478,7 @@ export function useAutocomplete(props) {
... | diff --git a/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx b/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
--- a/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
+++ b/packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx
@@ -1402,9 +1402,15 @@ describe('Joy <Autocomplete />', () => {
... | [material-ui][joy-ui][base-ui][Autocompelte] Highlighted index is broken when inserting new item
### Steps to reproduce
Link to live example: https://codesandbox.io/p/sandbox/mui-autocomplete-bug-94thpd?file=%2Fsrc%2FApp.js
Steps:
1. As soon as the component appears, press the bottom arrow to select the first item... | It's a bug. I also observed that it only occurs when the option is added to the beginning of the list. | 2024-02-28 16:39:10+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:18
WORKDIR /testbed
COPY package.json pnpm-lock.yaml ./
RUN npm install -g pnpm@9.4.0
RUN npx playwright install --with-deps
RUN pnpm install
COPY . .
RUN pnpm add -w -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @typ... | ['packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: onHighlightChange should pass to onHighlightChange the correct value after filtering', 'packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: disabled should disable the input', 'packages/mui-material/src... | ['packages/mui-material/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: options should keep focus on selected option when options updates and when options are provided as objects', 'packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx->Joy <Autocomplete /> prop: options should keep focus on selected op... | ['packages/pigment-react/tests/pigment.test.ts->zero-runtime test input file styled.input.js'] | pnpm cross-env NODE_ENV=test mocha packages/mui-material/src/Autocomplete/Autocomplete.test.js packages/mui-joy/src/Autocomplete/Autocomplete.test.tsx --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-base/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 41,651 | mui__material-ui-41651 | ['38178'] | 04c8786ad081c0e2bc3c596ab2baa879e49f6d94 | diff --git a/docs/pages/material-ui/api/tab-panel.json b/docs/pages/material-ui/api/tab-panel.json
--- a/docs/pages/material-ui/api/tab-panel.json
+++ b/docs/pages/material-ui/api/tab-panel.json
@@ -3,6 +3,7 @@
"value": { "type": { "name": "string" }, "required": true },
"children": { "type": { "name": "node"... | diff --git a/packages/mui-lab/src/TabPanel/TabPanel.test.tsx b/packages/mui-lab/src/TabPanel/TabPanel.test.tsx
--- a/packages/mui-lab/src/TabPanel/TabPanel.test.tsx
+++ b/packages/mui-lab/src/TabPanel/TabPanel.test.tsx
@@ -24,14 +24,17 @@ describe('<TabPanel />', () => {
],
}));
- it('renders a [role="tabpan... | restore component state in data grid when switching tabs
### Order ID or Support key 💳 (optional)
66023
### Duplicates
- [X] I have searched the existing issues
### Latest version
- [X] I have tested the latest version
### The problem in depth 🔍
If I use a TabPanel component that has a DataGridPro component as... | You need to change the `display` style to `none` of the TabPanel. In that way, it will kept mounted but not visible and the DataGrid won't lose its state.
Changing `display` to `none` would require me to manage the tab switching behaviour myself, obviating the usage of the TabPanel component. I am suggesting that the ... | 2024-03-25 20:06:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18 && npm install -g pnpm@8.15.7 && pnpm install && pnpm add -w -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util enzyme enzyme-adapte... | ['packages/mui-joy/src/AccordionDetails/AccordionDetails.test.tsx-><AccordionDetails /> MUI component API ref attaches the ref', 'packages/mui-system/src/Unstable_Grid/traverseBreakpoints.test.ts->traverse breakpoints custom breakpoints supports array', 'packages/mui-joy/src/styles/variantUtils.test.js->variant utils i... | ['packages/mui-lab/src/TabPanel/TabPanel.test.tsx-><TabPanel /> is [hidden] when TabPanel#value !== TabContext#value but does mount children when keepMounted'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18 && pnpm cross-env NODE_ENV=test mocha 'packages/**/*.test.{js,ts,tsx}' 'docs/**/*.test.{js,ts,tsx}' --exclude 'packages/pigment-css-react/**/*.test.{js,ts,tsx}' --reporter /testbed/custom-reporter.js && sh -c pnpm cross-env NODE_ENV=test mocha packages/mui-lab/src/TabPanel/TabPanel... | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 41,881 | mui__material-ui-41881 | ['41417'] | 357c50ed8784336fc4f6ad614fe796ed9033125e | diff --git a/packages/mui-material/src/Dialog/Dialog.js b/packages/mui-material/src/Dialog/Dialog.js
--- a/packages/mui-material/src/Dialog/Dialog.js
+++ b/packages/mui-material/src/Dialog/Dialog.js
@@ -182,6 +182,7 @@ const Dialog = React.forwardRef(function Dialog(inProps, ref) {
fullWidth = false,
maxWidth... | diff --git a/packages/mui-material/src/Dialog/Dialog.test.js b/packages/mui-material/src/Dialog/Dialog.test.js
--- a/packages/mui-material/src/Dialog/Dialog.test.js
+++ b/packages/mui-material/src/Dialog/Dialog.test.js
@@ -187,6 +187,28 @@ describe('<Dialog />', () => {
expect(onClose.callCount).to.equal(1);
... | [material-ui][Dialog] Specifying onClick prop disables backdrop clicks
### Steps to reproduce
[Link to live example](https://codesandbox.io/p/sandbox/smoosh-cache-fdm94z?layout=%257B%2522sidebarPanel%2522%253A%2522EXPLORER%2522%252C%2522rootPanelGroup%2522%253A%257B%2522direction%2522%253A%2522horizontal%2522%252C%252... | I agree it's a bug.
> Invoke it from within `handleBackdropClick` [here](https://github.com/mui/material-ui/blob/master/packages/mui-material/src/Dialog/Dialog.js#L213) (if provided in props) instead of grouping it with `...others`.
Where to call `handleBackdropClick` then?
Would the following fix work:
```diff
... | 2024-04-13 20:58:51+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 18 && npm install -g pnpm@8.15.7 && pnpm install && pnpm add -w -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @types/format-util enzyme enzyme-adapte... | ['packages/mui-joy/src/AccordionDetails/AccordionDetails.test.tsx-><AccordionDetails /> MUI component API ref attaches the ref', 'packages/mui-system/src/Unstable_Grid/traverseBreakpoints.test.ts->traverse breakpoints custom breakpoints supports array', 'packages/mui-joy/src/styles/variantUtils.test.js->variant utils i... | ['packages/mui-material/src/Dialog/Dialog.test.js-><Dialog /> backdrop calls onBackdropClick when onClick callback also exists'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18 && pnpm cross-env NODE_ENV=test mocha 'packages/**/*.test.{js,ts,tsx}' 'docs/**/*.test.{js,ts,tsx}' --exclude 'packages/pigment-css-react/**/*.test.{js,ts,tsx}' --reporter /testbed/custom-reporter.js && sh -c pnpm cross-env NODE_ENV=test mocha packages/mui-material/src/Dialog/Dialo... | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 42,412 | mui__material-ui-42412 | ['42252'] | b8a28e13dc0821314700f1aefc9f8e1134cf9034 | diff --git a/packages/mui-material/src/styles/responsiveFontSizes.js b/packages/mui-material/src/styles/responsiveFontSizes.js
--- a/packages/mui-material/src/styles/responsiveFontSizes.js
+++ b/packages/mui-material/src/styles/responsiveFontSizes.js
@@ -34,6 +34,11 @@ export default function responsiveFontSizes(themeI... | diff --git a/packages/mui-material/src/styles/responsiveFontSizes.test.js b/packages/mui-material/src/styles/responsiveFontSizes.test.js
--- a/packages/mui-material/src/styles/responsiveFontSizes.test.js
+++ b/packages/mui-material/src/styles/responsiveFontSizes.test.js
@@ -59,6 +59,19 @@ describe('responsiveFontSizes'... | responsiveFontSizes crashes when one of the variants is disabled
### Steps to reproduce
Link to live example:
https://stackblitz.com/edit/github-o8g8fe?file=src%2FApp.tsx
Steps:
1. Create a theme
2. Mark one of the default typography variants as undefined
3. use responsiveFontSizes on the theme
### Curre... | This is to be expected since we spread those variant definitions in a lot of places and there are no `undefined` checks. You could instead try to make them as empty object (`{}`) instead of undefined and see if that works.
But this way I cant have the type as undefined in Typescript, right? and so this variants will st... | 2024-05-27 05:23:53+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:18
WORKDIR /testbed
COPY package.json pnpm-lock.yaml ./
RUN npm install -g pnpm@8.15.8
RUN npx playwright install --with-deps
RUN pnpm install
COPY . .
RUN pnpm add -w -D @types/prop-types @types/react-dom @types/testing-library__react @types/sinon @types/chai @types/chai-dom @ty... | ['packages/mui-material/src/styles/responsiveFontSizes.test.js->responsiveFontSizes when requesting a responsive typography with non unitless line height and alignment should throw an error, as this is not supported', 'packages/mui-material/src/styles/responsiveFontSizes.test.js->responsiveFontSizes should support unit... | ['packages/mui-material/src/styles/responsiveFontSizes.test.js->responsiveFontSizes should handle variants that have been reset to undefined'] | [] | pnpm cross-env NODE_ENV=test mocha packages/mui-material/src/styles/responsiveFontSizes.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/mui-material/src/styles/responsiveFontSizes.js->program->function_declaration:responsiveFontSizes"] |
tailwindlabs/tailwindcss | 88 | tailwindlabs__tailwindcss-88 | ['18', '18'] | 1ab8bfbe15bdc630aad637f77fac7155256f3b0c | diff --git a/docs/source/docs/functions-and-directives.blade.md b/docs/source/docs/functions-and-directives.blade.md
--- a/docs/source/docs/functions-and-directives.blade.md
+++ b/docs/source/docs/functions-and-directives.blade.md
@@ -8,7 +8,7 @@ Tailwind exposes a few custom CSS functions and directives that can be us... | diff --git a/__tests__/fixtures/tailwind-input-with-explicit-screen-utilities.css b/__tests__/fixtures/tailwind-input-with-explicit-screen-utilities.css
new file mode 100644
--- /dev/null
+++ b/__tests__/fixtures/tailwind-input-with-explicit-screen-utilities.css
@@ -0,0 +1,11 @@
+@responsive {
+ .example {
+ ... | Screen-Utilities – problem with other postcss plugins
Hey there,
I love my utilities to be marked as ```!important``` because i've seen some people overwriting utilities (which is more than bad). If specitifity of e.g. a bem-item is higher the utility gets overridden.
## Example:
```css
.mx-auto { … }
/* t... | I think this is a reasonable idea.
What if we did something like this:
- Add an optional marker like `@tailwind screen-utilities` and in the processing phase where we generate those utilities, we first looked for that marker and if it was present, output the screen specific utilities there
- If that marker is ... | 2017-11-03 18:47:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/sanity.test.js->generates the right CSS',... | ['/testbed/__tests__/sanity.test.js->generates the right CSS with implicit screen utilities'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 109 | tailwindlabs__tailwindcss-109 | ['108'] | 9210b7f747d73888a6da5dc554e627f01e2c7265 | diff --git a/defaultConfig.js b/defaultConfig.js
--- a/defaultConfig.js
+++ b/defaultConfig.js
@@ -204,6 +204,7 @@ module.exports = {
'Fira Sans',
'Droid Sans',
'Helvetica Neue',
+ 'sans-serif',
],
'serif': [
'Constantia',
| diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -672,7 +672,7 @@ button,
}
.font-sans {
- font-family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen, Ubuntu, Canta... | .font-sans missing sans-serif
So the defaultConfig `.font-sans` font stack doesn't have `sans-serif` as the last fallback.
Although be unlikely that every font is missing, but if so the font stack actually falls back to Times New Roman on Chrome and Firefox (and most likely others).
ps.: Actually the only windows d... | Yeah, good point @tlgreg. I'll add that. | 2017-11-06 12:27:45+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 116 | tailwindlabs__tailwindcss-116 | ['112'] | ca366ee12d1f0f9bba4ae8ada0ccb43f865f84aa | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -528,6 +528,14 @@ iframe {
* Tailwind custom reset styles
*/
+*,
+*::before,
+*::after {
+ border-width: 0;
+ border-style: solid;
+ border-color: config('borderColors.default', currentColor);
+}
+
textarea {... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -528,6 +528,14 @@ iframe {
* Tailwind custom reset styles
*/
+*,
+*::before,
+*::after {
+ border-width: 0;
+ border-style: so... | Border Styles
`.border-dotted` is outputting `border-width: 0` due to the `borderStylesReset` (afaict). This means that `border-dotted` and `border-dashed` output `border-width: 0` nullifying the border style (as it removes the border).
Is this a bug or am I not understanding something? I can get `class=".border-dot... | null | 2017-11-06 16:20:37+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["src/generators/borderWidths.js->program->function_declaration:defaultBorder", "src/generators/borderWidths.js->program->function_declaration:sizedBorder"] |
tailwindlabs/tailwindcss | 119 | tailwindlabs__tailwindcss-119 | ['118'] | 7b5c4412e8f4333054fa4820775f279c4dd69361 | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -536,7 +536,7 @@ svg { fill: currentColor; }
button, input, optgroup, select, textarea { font-family: inherit; }
-input::placeholder {
+input::placeholder, textarea::placeholder {
color: inherit;
opacity... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -548,7 +548,8 @@ textarea {
font-family: inherit;
}
-input::placeholder {
+input::placeholder,
+textarea::placeholder {
color... | Default placeholder color discrepancy
The placeholder text for a textarea seems to be a different color from that of the inputs.
_Screenshot from Chrome Canary 64.0.3260.0_... | null | 2017-11-06 17:09:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 165 | tailwindlabs__tailwindcss-165 | ['159'] | 6bc3b0a9dd53f77555418b7b18d9b85ae7902c6e | diff --git a/src/generators/cursor.js b/src/generators/cursor.js
--- a/src/generators/cursor.js
+++ b/src/generators/cursor.js
@@ -3,6 +3,7 @@ import defineClasses from '../util/defineClasses'
export default function() {
return defineClasses({
'cursor-auto': { cursor: 'auto' },
+ 'cursor-default': { cursor:... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -3533,6 +3533,10 @@ button,
cursor: auto;
}
+.cursor-default {
+ cursor: default;
+}
+
.cursor-pointer {
cursor: pointer;
... | More cursor helpers
<!--
👋 Hey, thanks for taking an interest in Tailwind!
Please only open an issue here if you have a bug to report or a feature proposal you'd like to discuss.
If you need help, have questions about best practices, or want to start a discussion about anything else related to Tailwind, open ... | I think this is mostly because the ones you most commonly use are `pointer` and `not-allowed`, plus we have `auto` to set it back to the browser default.
Adding all the options would simply add bloat to the framework, and not really add much extra value. Plus, it's trivial to [add new utilities](https://tailwindcss.... | 2017-11-09 14:59:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/defineClasses.test.js->it generates a set... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 188 | tailwindlabs__tailwindcss-188 | ['204'] | 5e6bfb2f9e6aa220262d9b90c19bb46463829c9a | diff --git a/defaultConfig.js b/defaultConfig.js
--- a/defaultConfig.js
+++ b/defaultConfig.js
@@ -410,16 +410,19 @@ module.exports = {
| is provided, it will be made available as the non-suffixed `.rounded`
| utility.
|
- | Class name: .rounded{-radius?}
+ | If your scale includes a `0` value to reset alrea... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -2112,44 +2112,204 @@ button,
border-style: none;
}
-.rounded {
- border-radius: .25rem;
+.rounded-none {
+ border-radius: 0;
... | Feature: target individual corners when rounding
Hey guys,
Looks like there are no options yet to target individual corners with `rounded`.
Would it help if I make a PR to add the following?:
`.rounded-tl` - top left
`.rounded-tr` - top right
`.rounded-bl` - bottom left
`.rounded-br` - bottom right
| null | 2017-11-11 18:54:37+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/testbedlyClassPrefix.test.js->it prefixes... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["src/generators/rounded.js->program->function_declaration:sizedBorder", "src/generators/rounded.js->program->function_declaration:sideVariants"] |
tailwindlabs/tailwindcss | 211 | tailwindlabs__tailwindcss-211 | ['210'] | a33596831e8762a985aad6902539c108d0ddfc82 | diff --git a/src/generators/spacing.js b/src/generators/spacing.js
--- a/src/generators/spacing.js
+++ b/src/generators/spacing.js
@@ -2,93 +2,78 @@ import _ from 'lodash'
import defineClasses from '../util/defineClasses'
function definePadding(padding) {
- return _.flatMap(padding, (size, modifier) => {
- retu... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -2680,25 +2680,36 @@ button,
max-height: 100vh;
}
-.pt-0 {
- padding-top: 0;
+.p-0 {
+ padding: 0;
}
-.pr-0 {
- padding-ri... | Unexpected padding specificity due to rule definition order
I noticed that `.pl-0` is defined _before_ `.p-4`, and thus they cannot be used together in order to set general-then-more-specific styles, e.g.
```
<div id="foo" class="p-4 pl-0">foo</div>
```
Expected: `#foo { left-padding: 0; }`
Actual: `#foo { l... | We can definitely look into tweaking the order these are defined to make that possible. It's hard to make this always work for everyone exactly as expected though, so generally we recommend avoiding using colliding styles, instead setting them separately:
```
<div class="py-4 pr-4"></div>
```
I think we can fix... | 2017-11-16 18:22:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/testbedlyClassPrefix.test.js->it prefixes... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Refactoring | false | true | false | false | 3 | 0 | 3 | false | false | ["src/generators/spacing.js->program->function_declaration:defineNegativeMargin", "src/generators/spacing.js->program->function_declaration:definePadding", "src/generators/spacing.js->program->function_declaration:defineMargin"] |
tailwindlabs/tailwindcss | 216 | tailwindlabs__tailwindcss-216 | ['215'] | d9c3f7b6cf3584858ea59bb191c87c95b6efc6f7 | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -535,11 +535,10 @@ fieldset {
*
* We can remove this when the reversion is in a normal Chrome release.
*/
-input[type="button" i],
-input[type="submit" i],
-input[type="reset" i],
-input[type="file" i]::-webkit-f... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -535,11 +535,10 @@ fieldset {
*
* We can remove this when the reversion is in a normal Chrome release.
*/
-input[type="button" i... | Border-radius preflight is always aplied
When I have a button: `<input type="button">` and apply the `rounded` class to it, it will still always be `border-radius: 0`.
The css that takes the highest priority is in the preflight: https://github.com/tailwindcss/tailwindcss/blob/be3f9d38505ff7be9e5f507c054c08d5cc221960... | Yeah, they have an element in the selector too.
This would be the best I think without fighting specificity and not increasing the size of utilities:
```css
input[type="button" i]:not([class*="rounded" i]),
input[type="submit" i]:not([class*="rounded" i]),
input[type="reset" i]:not([class*="rounded" i]),
input[... | 2017-11-18 15:39:14+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/importsConfig.test.js->it can accept a config file', '/testbed/__tests__/focusableAtRule.test.js->it adds a focusable variant to each nested class definition', '/testbed/__tests__/testbedlyClassPrefix.test.js->it prefixes... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 236 | tailwindlabs__tailwindcss-236 | ['234'] | b696cbcbf00a1cb1d13f409fc2ca69e63600b6b8 | diff --git a/src/generators/position.js b/src/generators/position.js
--- a/src/generators/position.js
+++ b/src/generators/position.js
@@ -6,19 +6,23 @@ export default function() {
fixed: { position: 'fixed' },
absolute: { position: 'absolute' },
relative: { position: 'relative' },
- 'pin-t': { top: 0... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -3413,19 +3413,17 @@ button,
position: relative;
}
-.pin-t {
- top: 0;
+.pin-none {
+ top: auto;
+ right: auto;
+ bottom: au... | FR: Unsetting pin utilities
Right now it's not possible to "undo" pin properties of tailwind, for example if you want to pin something to the left, but on a different breakpoint pin it to the right:
`<div class="absolute pin-l sm:pin-r">Some thing</div>`
This will just cause the div to be full width, not pin it t... | Or as there is already a `pin-x` and `pin-y`, maybe `auto` the opposite side by default?
Though that adds unnecessary properties in most cases, so yeah, new classes sound better for me too. | 2017-11-24 14:58:59+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/mergeConfigWithDefaults.test.js->user modules are merged with default modules', '/testbed/__tests__/generateModules.test.js->variants can be different for each module', '/testbed/__tests__/configFunction.test.js->a default value can be provided', '/testbed/__tests__/focusableAtRule.test.js->it adds... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 416 | tailwindlabs__tailwindcss-416 | ['413'] | 7831312c122fae4939744bfcf0d774f7d9927d8d | diff --git a/src/generators/textStyle.js b/src/generators/textStyle.js
--- a/src/generators/textStyle.js
+++ b/src/generators/textStyle.js
@@ -3,7 +3,7 @@ import defineClasses from '../util/defineClasses'
export default function() {
return defineClasses({
italic: { 'font-style': 'italic' },
- roman: { 'font... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -4205,7 +4205,7 @@ button,
font-style: italic;
}
-.roman {
+.not-italic {
font-style: normal;
}
@@ -4251,7 +4251,7 @@ butt... | Font styles and weights naming
Hi! I’m testing Tailwind, and have a question about some class naming.
I was expecting these rules to be declared by these classes:
- `font-style: normal` from `.font-normal` or `.normal`
- `font-weight: regular` from `.font-regular` or `.regular`
But Tailwind works this way:
- `... | You can change `.font-normal` to `.font-regular` in your own config if you like; we chose the font weight names based on this document from the W3C:
https://www.w3.org/TR/css-fonts-3/#font-weight-numeric-values
The `.roman` situation is admittedly more annoying. We wanted `.italic` for italicized text, so similar... | 2018-03-12 16:16:52+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/parseObjectStyles.test.js->it parses nested pseudo-selectors', '/testbed/__tests__/processPlugins.test.js... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Refactoring | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 417 | tailwindlabs__tailwindcss-417 | ['392'] | 02bac50589b69d0159c3d71fa1e4b0b3c10cf413 | diff --git a/src/lib/substituteVariantsAtRules.js b/src/lib/substituteVariantsAtRules.js
--- a/src/lib/substituteVariantsAtRules.js
+++ b/src/lib/substituteVariantsAtRules.js
@@ -48,7 +48,7 @@ export default function(config) {
atRule.before(atRule.clone().nodes)
- _.forEach(['focus', 'hover', 'group-hov... | diff --git a/__tests__/variantsAtRule.test.js b/__tests__/variantsAtRule.test.js
--- a/__tests__/variantsAtRule.test.js
+++ b/__tests__/variantsAtRule.test.js
@@ -69,9 +69,9 @@ test('it can generate group-hover variants', () => {
})
})
-test('it can generate hover and focus variants', () => {
+test('it can genera... | State Variants Priority Order
## Foreword ##
People are (or at least, I am) increasingly excited about the possibility of having everything they need out of the box thanks to Tailwind, and state variants are a vital part of building user interfaces.
Tailwind already supports a bunch of them, but new ones are always p... | ## Hover vs. Focus ##
Currently, hover has a higher priority than focus. However, as discussed in the PR #379, this choice has his pros and cons.
As it is now, buttons have huge benefits, whilst inputs may lack consistency.
Are you relying on or fighting against this order?
| 2018-03-12 16:46:11+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/parseObjectStyles.test.js->it parses nested pseudo-selectors', '/testbed/__tests__/processPlugins.test.js... | ['/testbed/__tests__/variantsAtRule.test.js->it can generate all variants', '/testbed/__tests__/variantsAtRule.test.js->it wraps the output in a responsive at-rule if responsive is included as a variant'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 445 | tailwindlabs__tailwindcss-445 | ['439'] | 14f1ba6cb9133a9eaddf17f124b80b76882d1dbd | diff --git a/src/generators/overflow.js b/src/generators/overflow.js
--- a/src/generators/overflow.js
+++ b/src/generators/overflow.js
@@ -8,6 +8,10 @@ export default function() {
'overflow-scroll': { overflow: 'scroll' },
'overflow-x-auto': { 'overflow-x': 'auto' },
'overflow-y-auto': { 'overflow-y': 'a... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -3215,6 +3215,22 @@ button,
overflow-y: auto;
}
+.overflow-x-hidden {
+ overflow-x: hidden;
+}
+
+.overflow-y-hidden {
+ overf... | Add overflow-x-hidden and overflow-y-hidden
They're useful because sometimes you want `overflow-x-hidden overflow-y-auto` (the default `overflow-x` when `overflow-y` is set to `auto` is also `auto`).
| Yes! I just had to manually add these to a site I was working on yesterday. I guess @adamwathan will be okay with a PR that includes this as well as tests for them (probably a PR for the docs too).
@benface do you wanna take care of it or should I open the PR myself?
@hacknug Actually after posting this issue I real... | 2018-04-02 16:59:13+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/parseObjectStyles.test.js->it parses nested pseudo-selectors', '/testbed/__tests__/variantsAtRule.test.js... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 463 | tailwindlabs__tailwindcss-463 | ['459'] | 737e0628dac5f0bfde43337ecf35927375e842ea | diff --git a/defaultConfig.stub.js b/defaultConfig.stub.js
--- a/defaultConfig.stub.js
+++ b/defaultConfig.stub.js
@@ -852,6 +852,7 @@ module.exports = {
| - responsive
| - hover
| - focus
+ | - focus-within
| - active
| - group-hover
|
diff --git a/src/lib/substituteVariantsAtRules.js b/... | diff --git a/__tests__/variantsAtRule.test.js b/__tests__/variantsAtRule.test.js
--- a/__tests__/variantsAtRule.test.js
+++ b/__tests__/variantsAtRule.test.js
@@ -70,6 +70,27 @@ test('it can generate focus variants', () => {
})
})
+test('it can generate focus-within variants', () => {
+ const input = `
+ @var... | Feature Proposal: Add :focus-within @variant
I'd be useful to have a `:focus-within` variant, for better styling control in forms.
Functionality-wise, it'd work exactly the same has `focus`, `active`, and `hover`, as its rules would too follow the structure `.[variant-name]:[class-name]:[variant-name]`, with no side... | If I'm not mistaken, this’d only imply changes in these two:
https://github.com/tailwindcss/tailwindcss/blob/0f0a4f45e8e2122e99850d11ad2c576be249e366/src/lib/substituteVariantsAtRules.js#L21-L34
https://github.com/tailwindcss/tailwindcss/blob/0f0a4f45e8e2122e99850d11ad2c576be249e366/src/lib/substituteVariantsAtRu... | 2018-05-08 10:02:22+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/variantsAtRule.test.js->it can generate focus-within variants'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 537 | tailwindlabs__tailwindcss-537 | ['525'] | 95f1d90b70c4bb318f35ea475b903d07aee01fb4 | diff --git a/css/preflight.css b/css/preflight.css
--- a/css/preflight.css
+++ b/css/preflight.css
@@ -1,17 +1,15 @@
-/*! normalize.css v7.0.0 | MIT License | github.com/necolas/normalize.css */
+/*! normalize.css v8.0.0 | MIT License | github.com/necolas/normalize.css */
/* Document
============================... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -1,17 +1,15 @@
-/*! normalize.css v7.0.0 | MIT License | github.com/necolas/normalize.css */
+/*! normalize.css v8.0.0 | MIT License |... | Normalize.css 8.0.0
I love Tailwind CSS! Great job. Thank you.
Tailwind uses normalize.css 7.0.0. Version 8.0.0 is now available. Does Tailwind use 7.0.0 for some very specific reason?
I would create a pull request with an update, but normalize.css is outside `package.json` – it functions as a part of `css/prefli... | My interpretation of the preflight file is that you use it if you want as little trouble as possible to get started.
If you want to use another version of normalize.css, I suggest you add postcss-normalize to your project. And put the tailwind specific styles of preflight.css in your css file. Maybe you don't need a... | 2018-08-19 23:06:43+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Refactoring | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 550 | tailwindlabs__tailwindcss-550 | ['549', '549'] | 95f1d90b70c4bb318f35ea475b903d07aee01fb4 | diff --git a/src/generators/flexbox.js b/src/generators/flexbox.js
--- a/src/generators/flexbox.js
+++ b/src/generators/flexbox.js
@@ -90,13 +90,13 @@ export default function() {
'align-content': 'space-around',
},
'flex-1': {
- flex: '1',
+ flex: '1 1 0%',
},
'flex-auto': {
- ... | diff --git a/__tests__/fixtures/tailwind-output.css b/__tests__/fixtures/tailwind-output.css
--- a/__tests__/fixtures/tailwind-output.css
+++ b/__tests__/fixtures/tailwind-output.css
@@ -2963,15 +2963,15 @@ table {
}
.flex-1 {
- flex: 1;
+ flex: 1 1 0%;
}
.flex-auto {
- flex: auto;
+ flex: 1 1 auto;
}
.... | Improve IE compatibility for flex-1 utility
IE has trouble understanding our `flex-1` utility, perhaps we should avoid using the `flex: 1` shorthand and be more explicit. After some digging, I wound up on [this stackoverflow page](https://stackoverflow.com/questions/37386244/what-does-flex-1-mean) and am now overwritin... | This sounds like [Flexbug #6](https://github.com/philipwalton/flexbugs#flexbug-6).
Speaking of Flexbugs however, the above flex definition you're now using might cause [Flexbug #4](https://github.com/philipwalton/flexbugs#flexbug-4), which you could solve by using this:
```css
flex: 1 1 0%;
```
There's also lu... | 2018-09-10 18:41:47+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/sanity.test.js->generates the right CSS'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 553 | tailwindlabs__tailwindcss-553 | ['544'] | a63c976dc77137d6b67d718560a4b9847907880c | diff --git a/src/lib/substituteClassApplyAtRules.js b/src/lib/substituteClassApplyAtRules.js
--- a/src/lib/substituteClassApplyAtRules.js
+++ b/src/lib/substituteClassApplyAtRules.js
@@ -29,16 +29,29 @@ function normalizeClassName(className) {
return `.${escapeClassName(_.trimStart(className, '.'))}`
}
-function ... | diff --git a/__tests__/applyAtRule.test.js b/__tests__/applyAtRule.test.js
--- a/__tests__/applyAtRule.test.js
+++ b/__tests__/applyAtRule.test.js
@@ -192,3 +192,27 @@ test('you can apply utility classes that do not actually exist as long as they w
expect(result.warnings().length).toBe(0)
})
})
+
+test('you ca... | Allow prefix to be optional in @apply
Hi, I'm currently using tailwind with a prefix.
The one thing I don't particularly like is that it requires me to add the prefix before every @apply rule, which is more annoying the longer the prefix is.
I would love to be able to skip the prefix.
I think something like this w... | Would totally look at a PR for this, I think it's a reasonable suggestion 👍 | 2018-09-14 13:15:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/responsiveAtRule.test.js->it can generate responsive variants', '/testbed/__tests__/testbedlyAtRule.test.js->it does not match classes that have multiple rules', '/testbed/__tests__/cli.test.js->stdout o... | ['/testbed/__tests__/applyAtRule.test.js->you can apply utility classes without using the given prefix'] | [] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["src/lib/substituteClassApplyAtRules.js->program->function_declaration:findClass"] |
tailwindlabs/tailwindcss | 773 | tailwindlabs__tailwindcss-773 | ['771'] | 41d1c29d62dd3073e41e0d59de5e785cf3912d27 | diff --git a/src/lib/substituteScreenAtRules.js b/src/lib/substituteScreenAtRules.js
--- a/src/lib/substituteScreenAtRules.js
+++ b/src/lib/substituteScreenAtRules.js
@@ -1,17 +1,17 @@
import _ from 'lodash'
import buildMediaQuery from '../util/buildMediaQuery'
-export default function(config) {
+export default fun... | diff --git a/__tests__/screenAtRule.test.js b/__tests__/screenAtRule.test.js
new file mode 100644
--- /dev/null
+++ b/__tests__/screenAtRule.test.js
@@ -0,0 +1,47 @@
+import postcss from 'postcss'
+import plugin from '../src/lib/substituteScreenAtRules'
+import config from '../stubs/defaultConfig.stub.js'
+
+function r... | [beta.1] `No "md" screen found` error on build
I encountered a `No "md" screen found` error upon trying out `beta.1`. To attempt to rule out anything goofy I may have done with my own setup, here are reproduction steps using the Jigsaw Blog Starter Template upon which my site is based.
```shell
mkdir tailwind-next-... | What does your config file look like? My first guess is it’s still in the
old format.
On Sat, Mar 16, 2019 at 11:10 AM Michael Moussa <notifications@github.com>
wrote:
> I encountered a No "md" screen found error upon trying out beta.1. To
> attempt to rule out anything goofy I may have done with my own setup, here
> ... | 2019-03-16 18:20:21+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm install
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prebabelify
RUN . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npm run prepare
RUN . $NVM_DIR/nvm.sh && nvm alias default 8.9.1 && nvm use default
| ['/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->sele... | ['/testbed/__tests__/screenAtRule.test.js->it can generate media queries from configured screen sizes'] | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | . /usr/local/nvm/nvm.sh && nvm use 8.9.1 && npx jest --json --forceExit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 774 | tailwindlabs__tailwindcss-774 | ['770'] | 8699f39ce17693a73cb7669cd2476729baea17a9 | diff --git a/src/util/resolveConfig.js b/src/util/resolveConfig.js
--- a/src/util/resolveConfig.js
+++ b/src/util/resolveConfig.js
@@ -2,12 +2,15 @@ import mergeWith from 'lodash/mergeWith'
import isFunction from 'lodash/isFunction'
import defaults from 'lodash/defaults'
import map from 'lodash/map'
+import get from... | diff --git a/__tests__/resolveConfig.test.js b/__tests__/resolveConfig.test.js
--- a/__tests__/resolveConfig.test.js
+++ b/__tests__/resolveConfig.test.js
@@ -322,8 +322,8 @@ test('functions in the default theme section are lazily evaluated', () => {
magenta: 'magenta',
yellow: 'yellow',
},
- ... | Replacing all colors breaks the build
This bug occured while beta testing the new v1 config, it's not an issue in the stable release.
With the following config:
```js
module.exports = {
theme: {
colors: {
blue: "#084062",
red: "#ee585f",
paper: "#f5f2ea"
}
}
};
```
The b... | You can work around this by explicitly defining `borderColor` in your theme.
```
module.exports = {
theme: {
colors: {
blue: "#084062",
red: "#ee585f",
paper: "#f5f2ea"
},
borderColor: "#333",
}
}
```
Trying to think through the best way to solve this problem at a general... | 2019-03-16 20:32:00+00:00 | TypeScript | FROM node:8.17
WORKDIR /testbed
COPY . .
RUN npm install
RUN npm run prebabelify
RUN npm run prepare | ['/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->sele... | ['/testbed/__tests__/resolveConfig.test.js->functions in the user theme section are lazily evaluated', '/testbed/__tests__/resolveConfig.test.js->theme values in the extend section extend the existing theme', '/testbed/__tests__/resolveConfig.test.js->the theme function can use a default value if the key is missing', '... | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | npx jest --json --forceExit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["src/util/resolveConfig.js->program->function_declaration:resolveFunctionKeys"] |
tailwindlabs/tailwindcss | 849 | tailwindlabs__tailwindcss-849 | ['833'] | 4f58205d1d139dd2c296aaa8a01cb98383a7ea0a | diff --git a/src/util/configurePlugins.js b/src/util/configurePlugins.js
--- a/src/util/configurePlugins.js
+++ b/src/util/configurePlugins.js
@@ -1,7 +1,7 @@
export default function(pluginConfig, plugins) {
return Object.keys(plugins)
.filter(pluginName => {
- return pluginConfig[pluginName] !== false
+ ... | diff --git a/__tests__/configurePlugins.test.js b/__tests__/configurePlugins.test.js
--- a/__tests__/configurePlugins.test.js
+++ b/__tests__/configurePlugins.test.js
@@ -16,3 +16,15 @@ test('setting a plugin to false removes it', () => {
expect(configuredPlugins).toEqual(['fontSize', 'backgroundPosition'])
})
+
... | Ability to disable all core plugins (corePlugins: false?)
As discussed on Discord, it would be useful to be able to disable all core plugins without explicitly listing them all, for instance when using Tailwind in a test suite for a plugin. Adam suggested `corePlugins: false`.
| Looking for this as well! I use Tailwind to generate mini util files for use in Shadow DOM.
How can we provide a whitelist of plugins instead? | 2019-04-17 12:17:23+00:00 | TypeScript | FROM node:8.17
WORKDIR /testbed
COPY . .
RUN npm install
RUN npm run prebabelify
RUN npm run prepare | ['/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can optionally be ignored for utilities', '/testbed/__tests__/testbedlyAtRule.test.js->sele... | ['/testbed/__tests__/configurePlugins.test.js->passing only false removes all plugins'] | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
tailwindlabs/tailwindcss | 853 | tailwindlabs__tailwindcss-853 | ['850'] | daea6623fd691d52e6ff1ce440f6a7d29b9d3adb | diff --git a/src/util/configurePlugins.js b/src/util/configurePlugins.js
--- a/src/util/configurePlugins.js
+++ b/src/util/configurePlugins.js
@@ -1,9 +1,9 @@
export default function(pluginConfig, plugins) {
- return Object.keys(plugins)
- .filter(pluginName => {
- return pluginConfig !== false && pluginConfi... | diff --git a/__tests__/configurePlugins.test.js b/__tests__/configurePlugins.test.js
--- a/__tests__/configurePlugins.test.js
+++ b/__tests__/configurePlugins.test.js
@@ -28,3 +28,15 @@ test('passing only false removes all plugins', () => {
expect(configuredPlugins).toEqual([])
})
+
+test('passing an array whitel... | Ability to only enable specific core plugins
Right now you can disable all core plugins with `corePlugins: false` (thank you @adamwathan!) but [as Adam said](https://github.com/tailwindcss/tailwindcss/issues/833#issuecomment-484162018), it would be useful to have a "whitelisting" option to only enable one or a few core... | Would it make sense to also add a "blacklisting" option?
@hacknug All core plugins are enabled by default, so to blacklist you only have to do:
```
corePlugins: {
'backgroundColor': false,
'textColor': false,
}
```
Silly me. I keep mixing the old and new configs structures in my head haha
What about just ... | 2019-04-18 14:33:19+00:00 | TypeScript | FROM node:8.17
WORKDIR /testbed
COPY . .
RUN npm install
RUN npm run prebabelify
RUN npm run prepare | ['/testbed/__tests__/configurePlugins.test.js->passing only false removes all plugins', '/testbed/__tests__/processPlugins.test.js->plugins can add base styles with object syntax', '/testbed/__tests__/plugins/borderColor.test.js->colors can be a nested object', '/testbed/__tests__/processPlugins.test.js->important can ... | ['/testbed/__tests__/configurePlugins.test.js->passing an array whitelists plugins'] | ['/testbed/__tests__/cli.compile.test.js->compiles CSS file', '/testbed/__tests__/cli.test.js->compiles CSS file with autoprefixer'] | npx jest --json --forceExit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
coder/code-server | 3,277 | coder__code-server-3277 | ['2985'] | f8d8ad38c166d74332fb71adbce5f08c14bfc7e3 | diff --git a/lib/vscode/.eslintignore b/lib/vscode/.eslintignore
--- a/lib/vscode/.eslintignore
+++ b/lib/vscode/.eslintignore
@@ -19,3 +19,4 @@
# These are code-server code symlinks.
src/vs/base/node/proxy_agent.ts
src/vs/ipc.d.ts
+src/vs/server/common/util.ts
diff --git a/lib/vscode/src/vs/server/browser/client.ts... | diff --git a/test/unit/register.test.ts b/test/unit/register.test.ts
--- a/test/unit/register.test.ts
+++ b/test/unit/register.test.ts
@@ -22,11 +22,11 @@ describe("register", () => {
})
beforeEach(() => {
+ jest.clearAllMocks()
jest.mock("@coder/logger", () => loggerModule)
})
after... | Log out button should not appear if not using password
<!--
Hi there! 👋
Thanks for reporting a bug. Please see https://github.com/cdr/code-server/blob/main/docs/FAQ.md#how-do-i-debug-issues-with-code-server and include any logging information relevant to the issue.
Please search for existing issues before fil... | Good call! We didn't consider that when adding the Log out feature. Thanks for bringing this to our attention! Added to an upcoming milestone. | 2021-05-03 20:26:53+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:14
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/health.test.ts->/healthz', '/testbed/test/unit/cli.test.ts->should use existing if --new-window is set', "/testbed/test/unit/serviceWorker.test.ts->should call the proper callbacks for 'activate'", '/testbed/test/unit/register.test.ts->should log an error', '/testbed/test/unit/proxy.test.ts->should... | ['/testbed/test/unit/register.test.ts->register when navigator and serviceWorker are NOT defined should log an error'] | [] | yarn test:unit --json --silent | Bug Fix | false | true | false | false | 4 | 0 | 4 | false | false | ["src/browser/register.ts->program->function_declaration:registerServiceWorker", "lib/vscode/src/vs/workbench/browser/parts/titlebar/menubarControl.ts->program->class_declaration:CustomMenubarControl->method_definition:constructor", "src/common/util.ts->program->function_declaration:logError", "lib/vscode/src/vs/workbe... |
coder/code-server | 3,304 | coder__code-server-3304 | ['2200'] | 8e21eb51b318ff375477743460f1f62043aecc80 | diff --git a/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md b/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
--- a/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
+++ b/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
@@ -2,7 +2,7 @@
Please link to the issue this PR solves.
If there is no... | diff --git a/test/unit/node/util.test.ts b/test/unit/node/util.test.ts
new file mode 100644
--- /dev/null
+++ b/test/unit/node/util.test.ts
@@ -0,0 +1,147 @@
+describe("getEnvPaths", () => {
+ describe("on darwin", () => {
+ let ORIGINAL_PLATFORM = ""
+
+ beforeAll(() => {
+ ORIGINAL_PLATFORM = process.plat... | Fail to create tls-proxy for the second process.
<!--
Please see https://github.com/cdr/code-server/blob/master/doc/FAQ.md#how-do-i-debug-issues-with-code-server
and include any logging information relevant to the issue.
Please search for existing issues before filing.
If you can reproduce the issue on vanilla ... | Nice catch! One workaround is to handle TLS in a reverse proxy, then
code-server won't have to create the TLS proxy.
Maybe we should use a path in the user's data directory instead? Then we
won't have any permission issues or users stepping on other users' toes.
Or we could use a random path in /tmp which would... | 2021-05-06 23:24:26+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:14
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ['/testbed/test/unit/cli.test.ts->should use existing if --new-window is set', "/testbed/test/unit/serviceWorker.test.ts->should call the proper callbacks for 'activate'", '/testbed/test/unit/register.test.ts->should log an error', '/testbed/test/unit/routes/static.test.ts->should return a 404 for a nonexistent file', ... | ['/testbed/test/unit/node/util.test.ts->getEnvPaths on other platforms should return the env paths using envPaths when xdgBasedir is undefined', '/testbed/test/unit/node/util.test.ts->getEnvPaths on darwin should return the env paths using envPaths when xdgBasedir is undefined', '/testbed/test/unit/node/util.test.ts->g... | [] | yarn test:unit --json --silent | Bug Fix | false | false | false | true | 2 | 1 | 3 | false | false | ["src/node/util.ts->program->function_declaration:getEnvPaths", "src/node/socket.ts->program->class_declaration:SocketProxyProvider", "src/node/socket.ts->program->class_declaration:SocketProxyProvider->method_definition:startProxyServer"] |
coder/code-server | 4,430 | coder__code-server-4430 | ['4355'] | 605c3c63670c4f9ba94064e04a642a344f149a66 | diff --git a/src/node/routes/errors.ts b/src/node/routes/errors.ts
--- a/src/node/routes/errors.ts
+++ b/src/node/routes/errors.ts
@@ -6,7 +6,7 @@ import { WebsocketRequest } from "../../../typings/pluginapi"
import { HttpCode } from "../../common/http"
import { rootPath } from "../constants"
import { replaceTemplat... | diff --git a/test/unit/node/routes/errors.test.ts b/test/unit/node/routes/errors.test.ts
new file mode 100644
--- /dev/null
+++ b/test/unit/node/routes/errors.test.ts
@@ -0,0 +1,35 @@
+import express from "express"
+import { errorHandler } from "../../../../src/node/routes/errors"
+
+describe("error page is rendered fo... | Cross Site Scripting（XSS）vulnerability in code-server
<!--
Hi there! 👋
Thanks for reporting a bug.
Please search for existing issues before filing, as they may contain additional
information about the problem and descriptions of workarounds. Provide as much
information as you can, so that we can reproduce t... | @code-asher is this expected since the person would have to have access to the vm/machine running code-server?
@jsjoeio someone can send you a forged link that makes you execute arbitrary code in your code-server instance. See https://owasp.org/www-community/attacks/xss/
Yeah we should probably make a habit of escaping... | 2021-11-03 02:01:02+00:00 | TypeScript | FROM public.ecr.aws/docker/library/node:14
RUN apt-get update && apt-get install -y git build-essential g++ libx11-dev libkrb5-dev gnupg unzip curl wget software-properties-common && curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash ... | ["/testbed/test/unit/node/util.test.ts->should return ARGON2 for password with 'argon2'", '/testbed/test/unit/node/update.test.ts->should keep existing information', '/testbed/test/unit/node/routes/health.test.ts->/healthz (websocket)', '/testbed/test/unit/node/util.test.ts->should return true if is match', '/testbed/t... | ['/testbed/test/unit/node/routes/errors.test.ts->error page is rendered for text/html requests escapes any html in the error messages'] | ["/testbed/test/unit/node/cli.test.ts->shouldSpawnCliProcess should return true if 'uninstall-extension' passed in", "/testbed/test/unit/node/cli.test.ts->shouldSpawnCliProcess should return false if no 'extension' related args passed in", "/testbed/test/unit/node/cli.test.ts->shouldSpawnCliProcess should return true i... | yarn test:unit --json --silent | Security | true | false | false | false | 0 | 0 | 0 | false | false | [] |
Subsets and Splits
Top Repos by Test Count
Lists the top 1000 repositories by the number of entries, providing a basic count of entries per repository.
Unique Repo Selection
Lists unique repository names from the dataset, providing a basic overview of the repositories present.