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 | 15,436 | mui__material-ui-15436 | ['15435'] | 947853d0fde0d3048f653069bb1febe6dbde9577 | diff --git a/packages/material-ui/src/InputBase/Textarea.js b/packages/material-ui/src/InputBase/Textarea.js
--- a/packages/material-ui/src/InputBase/Textarea.js
+++ b/packages/material-ui/src/InputBase/Textarea.js
@@ -9,6 +9,19 @@ function getStyleValue(computedStyle, property) {
const useEnhancedEffect = typeof wi... | diff --git a/packages/material-ui/src/InputBase/Textarea.test.js b/packages/material-ui/src/InputBase/Textarea.test.js
--- a/packages/material-ui/src/InputBase/Textarea.test.js
+++ b/packages/material-ui/src/InputBase/Textarea.test.js
@@ -38,11 +38,19 @@ describe('<Textarea />', () => {
const getComputedStyleStub ... | [TextField] multiLine TextField loses cursor position
<!--- Provide a general summary of the issue in the Title above -->
Cursor jumps to the end in a multiLine TextField
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the f... | null | 2019-04-21 20:47:37+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/InputBase/Textarea.... | ['packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout should take the border into account with border-box', 'packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout should have at least "rowsMin" rows', 'packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout resiz... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputBase/Textarea.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 15,495 | mui__material-ui-15495 | ['8191'] | a97c70fcbd4891e283e2efa2ba9c067f524826be | diff --git a/packages/material-ui/src/ListItem/ListItem.js b/packages/material-ui/src/ListItem/ListItem.js
--- a/packages/material-ui/src/ListItem/ListItem.js
+++ b/packages/material-ui/src/ListItem/ListItem.js
@@ -30,7 +30,6 @@ export const styles = theme => ({
container: {
position: 'relative',
},
- // To... | diff --git a/packages/material-ui/test/integration/MenuList.test.js b/packages/material-ui/test/integration/MenuList.test.js
--- a/packages/material-ui/test/integration/MenuList.test.js
+++ b/packages/material-ui/test/integration/MenuList.test.js
@@ -51,19 +51,34 @@ function assertMenuItemTabIndexed(wrapper, tabIndexed... | Select menu does not fully implement keyboard controls
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox sh... | Given that this would require the component to hold internal state, rolling it in may not be the best move. Perhaps add a demo for this that hooks into the Input's onKeyUp handler though. Thoughts?
I'm glad we expose a native select version too that don't suffer from this issue.
>Material UI is an amazing asset, but in... | 2019-04-26 01:50:14+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation - preselected item should focus the third item', 'packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation should focus the secon... | ['packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration MenuList text-based keyboard controls should not move focus when no match', 'packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration MenuList text-based keyboard controls should not move focus when additional keys ma... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/MenuList.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/MenuList/MenuList.js->program->function_declaration:moveFocus", "packages/material-ui/src/MenuList/MenuList.js->program->function_declaration:textCriteriaMatches"] |
mui/material-ui | 15,526 | mui__material-ui-15526 | ['15515'] | 6ef44f1cf8fdd8c8670a25cbd4c16a54c332198f | diff --git a/packages/material-ui/src/utils/reactHelpers.js b/packages/material-ui/src/utils/reactHelpers.js
--- a/packages/material-ui/src/utils/reactHelpers.js
+++ b/packages/material-ui/src/utils/reactHelpers.js
@@ -14,15 +14,17 @@ export function setRef(ref, value) {
export function useForkRef(refA, refB) {
/... | diff --git a/packages/material-ui/src/utils/reactHelpers.test.js b/packages/material-ui/src/utils/reactHelpers.test.js
--- a/packages/material-ui/src/utils/reactHelpers.test.js
+++ b/packages/material-ui/src/utils/reactHelpers.test.js
@@ -2,6 +2,7 @@ import React from 'react';
import { assert } from 'chai';
import { ... | [Zoom] Not accepting child component
First of all, Thanks for giving this beautiful framework. It has always been a great experience to work with Material-UI.
Today, I updated my project to `@material-ui/core@next`. Successfully removed all deprecated props. But, failed to solve this issue. Prior to v4 this was work... | @eps1lon Would this change work for you? It doesn't break any test but solves the warning here.
```diff
--- a/packages/material-ui/src/utils/reactHelpers.js
+++ b/packages/material-ui/src/utils/reactHelpers.js
@@ -18,11 +18,13 @@ export function useForkRef(refA, refB) {
* This means react will call the old for... | 2019-04-30 06:46:38+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/utils/reactHelpers.test.js->utils/reactHelpers.js setRef can handle callback refs', 'packages/material-ui/src/utils/reactHelpers.test.js->utils/reactHelpers.js isMuiElement should be truthy for matching components', 'packages/material-ui/src/utils/reactHelpers.test.js->utils/reactHelpers.js s... | ['packages/material-ui/src/utils/reactHelpers.test.js->utils/reactHelpers.js useForkRef does nothing if none of the forked branches requires a ref'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/utils/reactHelpers.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/utils/reactHelpers.js->program->function_declaration:useForkRef"] |
mui/material-ui | 15,534 | mui__material-ui-15534 | ['15533'] | 02f135da5f4e51838994ddeea2d9474894f3f67d | diff --git a/docs/src/pages/css-in-js/advanced/advanced.md b/docs/src/pages/css-in-js/advanced/advanced.md
--- a/docs/src/pages/css-in-js/advanced/advanced.md
+++ b/docs/src/pages/css-in-js/advanced/advanced.md
@@ -484,7 +484,7 @@ generates the following class names you that can override:
.MuiButton-root { /* … */ }
... | diff --git a/packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js b/packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js
--- a/packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js
+++ b/packages/material-ui-styles/s... | [Switches] styling issue with global className
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should loo... | @timaxxer Thanks for reporting the problem. I'm having a look. | 2019-04-30 12:57:04+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js->createGenerateClassName should work without a classNamePrefix', 'packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js->createGenerateClassName production should output a short representation', '... | ['packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js->createGenerateClassName should generate global class names'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-styles/src/createGenerateClassName/createGenerateClassName.js->program->function_declaration:createGenerateClassName"] |
mui/material-ui | 15,578 | mui__material-ui-15578 | ['15565'] | 4516cafd6959fafccae96ca0bc70527d0fd5cf02 | diff --git a/docs/src/pages/customization/overrides/overrides.md b/docs/src/pages/customization/overrides/overrides.md
--- a/docs/src/pages/customization/overrides/overrides.md
+++ b/docs/src/pages/customization/overrides/overrides.md
@@ -83,51 +83,79 @@ const StyledButton = withStyles({
{{"demo": "pages/customizati... | diff --git a/packages/material-ui/src/styles/createMuiTheme.test.js b/packages/material-ui/src/styles/createMuiTheme.test.js
--- a/packages/material-ui/src/styles/createMuiTheme.test.js
+++ b/packages/material-ui/src/styles/createMuiTheme.test.js
@@ -101,11 +101,15 @@ describe('createMuiTheme', () => {
});
... | Overriding "selected" style in MuiListItem has side effect on MuiTabs
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Expected Behavior 🤔
Overri... | You can fix this by changing:
```
const theme = createMuiTheme({
overrides: {
MuiListItem: {
selected: { textDecoration: "underline" }
}
}
});
```
to:
```
const theme = createMuiTheme({
overrides: {
MuiListItem: {
root: {
"&$selected": { textDecoration: "underline... | 2019-05-03 10:37: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/styles/createMuiTheme.test.js->createMuiTheme should have a palette', 'packages/material-ui/src/styles/createMuiTheme.test.js->createMuiTheme shadows should override the array as expected', 'packages/material-ui/src/styles/createMuiTheme.test.js->createMuiTheme should have the custom palette'... | ['packages/material-ui/src/styles/createMuiTheme.test.js->createMuiTheme overrides should warn when trying to override an internal state the wrong way'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/styles/createMuiTheme.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/styles/createMuiTheme.js->program->function_declaration:createMuiTheme"] |
mui/material-ui | 15,581 | mui__material-ui-15581 | ['15580'] | 4516cafd6959fafccae96ca0bc70527d0fd5cf02 | diff --git a/packages/material-ui/src/Badge/Badge.d.ts b/packages/material-ui/src/Badge/Badge.d.ts
--- a/packages/material-ui/src/Badge/Badge.d.ts
+++ b/packages/material-ui/src/Badge/Badge.d.ts
@@ -3,8 +3,8 @@ import { StandardProps, PropTypes } from '..';
export interface BadgeProps
extends StandardProps<React.... | diff --git a/packages/material-ui/src/Badge/Badge.test.js b/packages/material-ui/src/Badge/Badge.test.js
--- a/packages/material-ui/src/Badge/Badge.test.js
+++ b/packages/material-ui/src/Badge/Badge.test.js
@@ -1,22 +1,23 @@
import React from 'react';
import { assert } from 'chai';
-import {
- createMount,
- create... | Badge Span rendered when badgeContent is undefined
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should... | @Naismith The current behavior depends on:
```js
Number(undefined) = NaN
Number(null) = 0
```
What do you think of this diff, would it work for you?
```diff
--- a/packages/material-ui/src/Badge/Badge.js
+++ b/packages/material-ui/src/Badge/Badge.js
@@ -92,7 +92,7 @@ const Badge = React.forwardRef(function Ba... | 2019-05-03 18:38:12+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: max should cap badgeContent', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: showZero should default to false', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> Material-UI component API prop: component can render another root compo... | ['packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: invisible should render with the invisible class when empty and not dot'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Badge/Badge.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 15,627 | mui__material-ui-15627 | ['15598'] | 1555e52367835946382fbf2a8f681de71318915d | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.js b/packages/material-ui/src/ButtonBase/ButtonBase.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.js
@@ -89,7 +89,18 @@ class ButtonBase extends React.Component {
});
componentDidMount()... | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.test.js b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.test.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
@@ -12,6 +12,8 @@ import {
} from '@material-ui/core/test-utils';
impor... | ButtonBase ownerdocument error
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x]... | Please fill out the issue template. We will need more information to look at this.
Here is the problem, in beta1 you quit the helper for get the owner document and right now if is null get the node get an error obiusly
```
componentDidMount() {
prepareFocusVisible(this.getButtonNode().ownerDocument);
if (th... | 2019-05-08 09:34:18+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> ripple should be enabled by default', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> root node should change the button component and add accessibility requirements', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> warnings throws with additional warnings on invalid `component` prop'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ButtonBase/ButtonBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/ButtonBase/ButtonBase.js->program->class_declaration:ButtonBase->method_definition:componentDidMount"] |
mui/material-ui | 15,644 | mui__material-ui-15644 | ['15509'] | 5d9a3c83e839098ba382f9c9236e3991a96d2d64 | diff --git a/docs/src/pages/components/toggle-button/ToggleButtonSizes.js b/docs/src/pages/components/toggle-button/ToggleButtonSizes.js
new file mode 100644
--- /dev/null
+++ b/docs/src/pages/components/toggle-button/ToggleButtonSizes.js
@@ -0,0 +1,51 @@
+import React from 'react';
+import FormatAlignLeftIcon from '@m... | diff --git a/packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js b/packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js
--- a/packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js
+++ b/packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js
@@ -67,6 +67,30 @@ describe('<ToggleButto... | [ToggleButtonGroup] - Feature Request - Add a size property
| null | 2019-05-09 20:51:14+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js-><ToggleButton /> prop: onChange should be called with the button value', 'packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js-><ToggleButton /> does forward refs', 'packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js-><ToggleButton ... | ['packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js-><ToggleButton /> should render a small button', 'packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js-><ToggleButton /> should render a large button'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/ToggleButton/ToggleButton.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 2 | 1 | 3 | false | false | ["docs/src/pages/components/toggle-button/ToggleButtons.js->program->class_declaration:ToggleButtons", "docs/src/pages/components/toggle-button/ToggleButtons.js->program->class_declaration:ToggleButtons->method_definition:render", "docs/src/pages/components/toggle-button/ToggleButtons.js->program->function_declaration:... |
mui/material-ui | 15,646 | mui__material-ui-15646 | ['15371'] | 048c9ced0258f38aa38d95d9f1cfa4c7b993a6a5 | diff --git a/packages/material-ui/src/Tabs/TabScrollButton.js b/packages/material-ui/src/Tabs/TabScrollButton.js
--- a/packages/material-ui/src/Tabs/TabScrollButton.js
+++ b/packages/material-ui/src/Tabs/TabScrollButton.js
@@ -1,3 +1,5 @@
+/* eslint-disable jsx-a11y/aria-role */
+
import React from 'react';
import Pr... | diff --git a/packages/material-ui/src/Tabs/Tabs.test.js b/packages/material-ui/src/Tabs/Tabs.test.js
--- a/packages/material-ui/src/Tabs/Tabs.test.js
+++ b/packages/material-ui/src/Tabs/Tabs.test.js
@@ -15,13 +15,13 @@ import TabScrollButton from './TabScrollButton';
import TabIndicator from './TabIndicator';
funct... | [Tabs] scrollButtons have an empty button error in compliance tools
I am using the wave extension tool on my chrome and it throws an empty button error on the right and left arrows of the scrollButtons.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe ... | @hgafoor Are you sure about the issue? These buttons are not reachable for a keyboard user nor for a screen reader. Do you confirm?
Can we trust this tool? I don't at 💯%. It shows an issue with the icon buttons while a `title` attribute is present:
![Capture d’écran 2019-04-16 à 17 53 48](https://user-images.g... | 2019-05-10 02:08:41+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons scroll button visibility states should not set scroll button states if difference is only one pixel', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: value indicator should render the indicator', 'packages/material-ui/src/Tabs/Tabs.t... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> scroll button behavior should call moveTabsScroll', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons scroll button visibility states should set only left scroll button state', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: scro... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/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 | 15,676 | mui__material-ui-15676 | ['12358'] | 0b10f8dddda23d49205c625e60578c12fd10d773 | diff --git a/packages/material-ui/src/Tabs/TabScrollButton.js b/packages/material-ui/src/Tabs/TabScrollButton.js
--- a/packages/material-ui/src/Tabs/TabScrollButton.js
+++ b/packages/material-ui/src/Tabs/TabScrollButton.js
@@ -12,7 +12,7 @@ export const styles = {
/* Styles applied to the root element. */
root: {... | diff --git a/packages/material-ui/src/Tabs/Tabs.test.js b/packages/material-ui/src/Tabs/Tabs.test.js
--- a/packages/material-ui/src/Tabs/Tabs.test.js
+++ b/packages/material-ui/src/Tabs/Tabs.test.js
@@ -398,14 +398,16 @@ describe('<Tabs />', () => {
it('should render scroll buttons automatically', () => {
... | [Tabs] Support "auto" as "scrollable" value
When using `<Tabs scrollable>` with few tabs, the first tab seems not properly aligned to the left. I need the ability to auto-set the `scrollable` behavior based on the screen width and the number of tabs.
<!-- Checked checkbox should look like this: [x] -->
- [x] This i... | @fzaninotto I'm personally using `scrollable={true} scrollButtons="off"` most of the time. Do you need to display the scroll buttons?
IMO It's not ideal on desktop screens to hide buttons, but I can live with that. Thanks for your answer.
> @fzaninotto I'm personally using `scrollable={true} scrollButtons="off"` most o... | 2019-05-13 12:47: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: value indicator should render the indicator', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: centered should render with the centered class', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: action should be able to access updateIndica... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons should render scroll buttons', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons should render scroll buttons automatically', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: scrollButtons should handle window ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tabs/Tabs.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Tabs/Tabs.js->program->class_declaration:Tabs"] |
mui/material-ui | 15,743 | mui__material-ui-15743 | ['15724'] | 997a8b5fe392c34db14b7f13203ab07db85c3238 | diff --git a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js
--- a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js
+++ b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js
@@ -26,7 +26,7 @@ function mapEventPr... | diff --git a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
--- a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
+++ b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
@@ -45,7 +45,7 @@... | ClickAwayListener triggers on clicking browser scrollbar
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox ... | We would need to detect in the ClickAwayListener if the click happened on the scrollbars. I don't know if this is possible.
Could be so kind and create a playground with a Menu with just many items so that we can verify whether this is an issue with this particular demo or the base Menu.
> We would need to detect i... | 2019-05-18 16:27:51+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Snackbar/Snackbar.test.js-><Snackbar /> prop: disableWindowBlurListener should not pause auto hide when disabled and window lost focus', 'packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: onClickAway should not be call when clicking inside', 'pa... | ['packages/material-ui/src/Snackbar/Snackbar.test.js-><Snackbar /> prop: onClose should be call when clicking away', 'packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: onClickAway should be call when clicking away'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js packages/material-ui/src/Snackbar/Snackbar.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/ClickAwayListener/ClickAwayListener.js->program->function_declaration:ClickAwayListener"] |
mui/material-ui | 15,839 | mui__material-ui-15839 | ['15837'] | ac392058af280e2247b6e5d4ca702d72839c4695 | diff --git a/packages/material-ui/src/Modal/Modal.js b/packages/material-ui/src/Modal/Modal.js
--- a/packages/material-ui/src/Modal/Modal.js
+++ b/packages/material-ui/src/Modal/Modal.js
@@ -8,10 +8,9 @@ import Portal from '../Portal';
import { createChainedFunction } from '../utils/helpers';
import { useForkRef } fr... | diff --git a/packages/material-ui/src/Modal/ModalManager.test.js b/packages/material-ui/src/Modal/ModalManager.test.js
--- a/packages/material-ui/src/Modal/ModalManager.test.js
+++ b/packages/material-ui/src/Modal/ModalManager.test.js
@@ -239,5 +239,24 @@ describe('ModalManager', () => {
modalManager.remove(moda... | ModalManager doesn't respect siblings that are already hidden
When clicking out of a modal that is popped-up, the ModalManager will unhide sibling nodes regardless of whether-or-not the sibling was hidden before the modal was popped-up. This causes nodes to become visible after clicking out of the modal.
Initial vie... | Can you provide a minimal reproducible example? e.g. a codesandbox or a stand-alone git repo.
@joshwooding Here you go:
https://codesandbox.io/s/blissful-blackburn-3n0ko
I might have a PR here in a minute. | 2019-05-24 20:15:44+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Modal/ModalManager.test.js->ModalManager should add a modal only once', 'packages/material-ui/src/Modal/ModalManager.test.js->ModalManager managing modals should add modal2', 'packages/material-ui/src/Modal/ModalManager.test.js->ModalManager container aria-hidden should remove aria-hidden on ... | ['packages/material-ui/src/Modal/ModalManager.test.js->ModalManager container aria-hidden should keep previous aria-hidden siblings hidden'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Modal/ModalManager.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 15 | 0 | 15 | false | false | ["packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:ariaHidden", "packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:getPaddingRight", "packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:handleNewContainer", "packages/material-ui/src/Moda... |
mui/material-ui | 15,851 | mui__material-ui-15851 | ['15842'] | 5cc9fb299ce8369ba2282e75c6d9aaea0e2852ba | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.js b/packages/material-ui/src/ButtonBase/ButtonBase.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.js
@@ -110,20 +110,7 @@ const ButtonBase = React.forwardRef(function ButtonBase(props, ref) {
... | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.test.js b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.test.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
@@ -637,7 +637,7 @@ describe('<ButtonBase />', () => {
PropTypes.r... | Jest + react-test-renderer snapshot testing fails with ButtonBase
Hi - I just upgraded to v4 and those test failures are really puzzling me.
It seems they all related with react-test-renderer, and most of them is caused by `ButtonBase` I believe. For some reason some tests are passing while similar tests are constantl... | Workaround explained in https://github.com/mui-org/material-ui/issues/15598#issuecomment-490963667. I'll leave this open because I might have an idea how to improve this situation.
@pallymore You can reproduce the same problem with:
```jsx
import React from 'react';
import renderer from 'react-test-renderer';
impor... | 2019-05-25 16:26: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> root node should change the button component and add accessibility requirements', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> prop: disabled should forward it to native buttons', 'packages/material-ui/src/ButtonBase/But... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> warnings warns on invalid `component` prop', 'packages/material-ui/src/utils/focusVisible.test.js->focus-visible polyfill focus inside shadowRoot should set focus state for shadowRoot children'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ButtonBase/ButtonBase.test.js packages/material-ui/src/utils/focusVisible.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/utils/focusVisible.js->program->function_declaration:useIsFocusVisible", "packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip"] |
mui/material-ui | 15,863 | mui__material-ui-15863 | ['15840'] | 831c6cc003e3bdc94d206b531a18d1816a55274c | diff --git a/packages/material-ui/src/Link/Link.d.ts b/packages/material-ui/src/Link/Link.d.ts
--- a/packages/material-ui/src/Link/Link.d.ts
+++ b/packages/material-ui/src/Link/Link.d.ts
@@ -17,7 +17,8 @@ export type LinkClassKey =
| 'underlineNone'
| 'underlineHover'
| 'underlineAlways'
- | 'button';
+ | 'b... | diff --git a/packages/material-ui/src/Link/Link.test.js b/packages/material-ui/src/Link/Link.test.js
--- a/packages/material-ui/src/Link/Link.test.js
+++ b/packages/material-ui/src/Link/Link.test.js
@@ -1,10 +1,17 @@
import React from 'react';
import { assert } from 'chai';
+import { spy } from 'sinon';
import { cre... | Button Link missing keyboard focus style
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like... | @ianschmitz What do you think of?:
```diff
diff --git a/packages/material-ui/src/Link/Link.js b/packages/material-ui/src/Link/Link.js
index 8d2cce4f4..ad565e212 100644
--- a/packages/material-ui/src/Link/Link.js
+++ b/packages/material-ui/src/Link/Link.js
@@ -3,6 +3,8 @@ import PropTypes from 'prop-types';
impo... | 2019-05-26 00:58:26+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Link/Link.test.js-><Link /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Link/Link.test.js-><Link /> should pass props to the <Typography> component', 'packages/material-ui/src/Link/Link.test.js-><Link /> Material-UI component API ref attac... | ['packages/material-ui/src/Link/Link.test.js-><Link /> keyboard focus should add the focusVisible class when focused'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Link/Link.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 15,864 | mui__material-ui-15864 | ['15858'] | c48ee6122e585087f9dd0b7cbafee1c8ac96e812 | diff --git a/packages/material-ui/src/IconButton/IconButton.d.ts b/packages/material-ui/src/IconButton/IconButton.d.ts
--- a/packages/material-ui/src/IconButton/IconButton.d.ts
+++ b/packages/material-ui/src/IconButton/IconButton.d.ts
@@ -4,8 +4,9 @@ import { SimplifiedPropsOf } from '../OverridableComponent';
decla... | diff --git a/packages/material-ui/src/IconButton/IconButton.test.js b/packages/material-ui/src/IconButton/IconButton.test.js
--- a/packages/material-ui/src/IconButton/IconButton.test.js
+++ b/packages/material-ui/src/IconButton/IconButton.test.js
@@ -77,6 +77,16 @@ describe('<IconButton />', () => {
assert.strictE... | [IconButton] Missing disableFocusRipple prop
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look ... | Unless this was intentional, I can open a PR to address this.
@lychyi You are raising an inconsistency in the code base, we have a `focusRipple` prop for the ButtonBase (where we don't want the ripple by default) and `disableFocusRipple` prop for the components that are built on top of it (where we want the ripple by d... | 2019-05-26 04:22: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Tab/Tab.test.js-><Tab /> prop: textColor should support the inherit value', 'packages/material-ui/src/IconButton/IconButton.test.js-><IconButton /> should have a ripple by default', 'packages/material-ui/src/Tab/Tab.test.js-><Tab /> Material-UI component API does spread props to the root comp... | ['packages/material-ui/src/Tab/Tab.test.js-><Tab /> should pass disableFocusRipple to ButtonBase', 'packages/material-ui/src/IconButton/IconButton.test.js-><IconButton /> should pass disableFocusRipple to ButtonBase'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/IconButton/IconButton.test.js packages/material-ui/src/Tab/Tab.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 15,947 | mui__material-ui-15947 | ['15689'] | 2b980645da9789854a36120c3bf1dfc5be9199aa | diff --git a/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js b/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js
--- a/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js
+++ b/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js
@@ -1,5 +1,3 @@
-/* eslint-disable consistent-this */... | diff --git a/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js b/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js
--- a/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js
+++ b/packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js
@@ -137,7 +137,7 @@ describe('<Sw... | Swipeable drawer not working on ios
<!--- Provide a general summary of the issue in the Title above -->
I can't get the swipeable drawer to open on swipe either on an actual iphone or using chrome dev tools with an iphone model selected. The main difference between simulation iphone and android seems to be that ios ha... | This is expected behavior. The reasons are outlined under https://material-ui.com/demos/drawers/#swipeable-temporary-drawer.
The only thing I recognized is that the full page is swiping once the drawer is open and not just the drawer. Maybe add a preventDefault when swiping? /cc @oliviertassinari
> I can't get the ... | 2019-05-29 21:06:14+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> swipe to open anchor=left should let user scroll the page', 'packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> should render a Drawer and a SwipeArea', 'packages/material-ui/src/SwipeableDrawer/Sw... | ['packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> warnings warns if a component for the Backdrop is used that cant hold a ref', 'packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> warnings warns if a component for the Paper is used that cant hold ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 15 | 1 | 16 | false | false | ["packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer->method_definition:removeTouchStart", "packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer->method_definition:componentDidMount", "packages/material-ui/src/Swipea... |
mui/material-ui | 16,004 | mui__material-ui-16004 | ['15922'] | b185d462112b6866263942b869b7e145f22da674 | diff --git a/docs/src/pages/components/popper/SimplePopper.js b/docs/src/pages/components/popper/SimplePopper.js
--- a/docs/src/pages/components/popper/SimplePopper.js
+++ b/docs/src/pages/components/popper/SimplePopper.js
@@ -12,7 +12,7 @@ const useStyles = makeStyles(theme => ({
},
}));
-function SimplePopper()... | diff --git a/packages/material-ui/src/Popper/Popper.test.js b/packages/material-ui/src/Popper/Popper.test.js
--- a/packages/material-ui/src/Popper/Popper.test.js
+++ b/packages/material-ui/src/Popper/Popper.test.js
@@ -215,7 +215,7 @@ describe('<Popper />', () => {
it('should warn if anchorEl is not valid', () => ... | Popper faked reference object props validation fails
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox shou... | Sounds like PropTypes.shap would be the better candidate here. Our typescript types need adjustment as well though and I'm not sure where we draw the boundary. If we only require the properties we currently use we might block important bug fixes in the future (layout computation is always a bit tricky across browsers).... | 2019-06-02 21:31: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip top-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip bottom-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> Ma... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> warnings should warn if anchorEl is not valid'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popper/Popper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/components/popper/SimplePopper.js->program->function_declaration:SimplePopper"] |
mui/material-ui | 16,069 | mui__material-ui-16069 | ['15802'] | 41f17228191df0ccd9c51fb3a090ec172018dc7b | diff --git a/packages/material-ui/src/Popper/Popper.d.ts b/packages/material-ui/src/Popper/Popper.d.ts
--- a/packages/material-ui/src/Popper/Popper.d.ts
+++ b/packages/material-ui/src/Popper/Popper.d.ts
@@ -1,5 +1,5 @@
import * as React from 'react';
-import { ReferenceObject } from 'popper.js';
+import PopperJs, { Re... | diff --git a/packages/material-ui/src/Popper/Popper.test.js b/packages/material-ui/src/Popper/Popper.test.js
--- a/packages/material-ui/src/Popper/Popper.test.js
+++ b/packages/material-ui/src/Popper/Popper.test.js
@@ -5,6 +5,7 @@ import PropTypes from 'prop-types';
import { createMount } from '@material-ui/core/test-... | Popper can't update position when content height changed
<img width="640" alt="屏幕快照 2019-05-23 下午5 33 43" src="https://user-images.githubusercontent.com/6634415/58242214-f6b73b00-7d80-11e9-8b8a-3833686e08a8.png">
<img width="567" alt="屏幕快照 2019-05-23 下午5 33 50" src="https://user-images.githubusercontent.com/6634415/58... | @oyb81076 I had to solve this problem with #15703. I think that we should extract the changes. We should fix this Popper limitation independently from the rewriting the Slider. Would you be interested in isolating the logic with a pull request? | 2019-06-05 13:10:26+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip top-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip bottom-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> Ma... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: popperRef should return a ref'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popper/Popper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,137 | mui__material-ui-16137 | ['16136'] | adaa66d3737b563c6f88df2fe7e77671287bcf8d | diff --git a/docs/src/pages/components/selects/CustomizedSelects.js b/docs/src/pages/components/selects/CustomizedSelects.js
--- a/docs/src/pages/components/selects/CustomizedSelects.js
+++ b/docs/src/pages/components/selects/CustomizedSelects.js
@@ -19,7 +19,6 @@ const BootstrapInput = withStyles(theme => ({
back... | diff --git a/packages/material-ui/src/Select/SelectInput.test.js b/packages/material-ui/src/Select/SelectInput.test.js
--- a/packages/material-ui/src/Select/SelectInput.test.js
+++ b/packages/material-ui/src/Select/SelectInput.test.js
@@ -41,7 +41,7 @@ describe('<SelectInput />', () => {
it('should render a correc... | Down arrow in NativeSelect OutlinedInput is not clickable
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox... | null | 2019-06-10 14:37: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ["packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed ArrowUp key on select", "packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed key on select", 'packages/material-ui/src/Select/SelectInput.... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> should render a correct top element'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,142 | mui__material-ui-16142 | ['11696'] | 85058cc4750d18fe7c9ed812090d19cf58af8a25 | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.js b/packages/material-ui/src/ButtonBase/ButtonBase.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.js
@@ -92,6 +92,7 @@ const ButtonBase = React.forwardRef(function ButtonBase(props, ref) {
... | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.test.js b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.test.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
@@ -113,6 +113,7 @@ describe('<ButtonBase />', () => {
'onMouseD... | [ButtonBase] Ripple Effect is duplicated when dragging an image
- [x] This is a v1.x issue (v0.x is no longer maintained).
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate. (The issue seems similar to #7537)
## Expected Beh... | @runewake2 The ripple disappear as soon as your mouse leaves the button base. I think that we are good here.
Plus the `onMouseUp` event doesn't trigger when dragging the image. I'm not sure we can do anything about it.
@runewake2 Try a few small click-drags within the ButtonBase one after the next. Then, each time you ... | 2019-06-10 18:08:47+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> root node should change the button component and add accessibility requirements', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> prop: disabled should forward it to native buttons', 'packages/material-ui/src/ButtonBase/But... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> ripple interactions should stop the ripple when dragging has finished'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ButtonBase/ButtonBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,196 | mui__material-ui-16196 | ['16184'] | 1d01a824065cfd5fc784002e77dc7ec38b5db474 | diff --git a/docs/src/modules/components/AppTableOfContents.js b/docs/src/modules/components/AppTableOfContents.js
--- a/docs/src/modules/components/AppTableOfContents.js
+++ b/docs/src/modules/components/AppTableOfContents.js
@@ -122,7 +122,7 @@ function useThrottledOnScroll(callback, delay) {
React.useEffect(() ... | diff --git a/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js b/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js
--- a/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js
+++ b/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js
@@ -48,33 +48,117 @@ describe('useMediaQuery', ()... | Regression: withWidth fails on the server side because of useMediaQuery
<!--- Provide a general summary of the issue in the Title above -->
Since #15678, the `withWidth()` HOC fails on the server-side (in unit tests run with react-testing-library) with the following error:
> TypeError: window.matchMedia is not a fu... | @fzaninotto If you are mounting the components, you need the browser API to be available. It seems that JSDOM doesn't implement it yet: https://github.com/jsdom/jsdom/blob/94774014e2244730f24d1fcb8c40d8fee3ea6b75/test/web-platform-tests/to-upstream/html/browsers/the-window-object/window-properties-dont-upstream.html#L1... | 2019-06-12 22:36:10+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | [] | ['packages/material-ui/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery without feature should work without window.matchMedia available', 'packages/material-ui/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery with feature should try to reconcile only the first time', 'packages/material-ui/src/useMediaQuery/... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/useMediaQuery/useMediaQuery.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/useMediaQuery/useMediaQuery.js->program->function_declaration:useMediaQuery", "docs/src/modules/components/AppTableOfContents.js->program->function_declaration:useThrottledOnScroll"] |
mui/material-ui | 16,250 | mui__material-ui-16250 | ['16240'] | 564aed388329ad75da7b1f5850e0a3bf24f25e56 | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.js b/packages/material-ui/src/ButtonBase/ButtonBase.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.js
@@ -92,7 +92,7 @@ const ButtonBase = React.forwardRef(function ButtonBase(props, ref) {
... | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.test.js b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.test.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
@@ -248,7 +248,7 @@ describe('<ButtonBase />', () => {
it('shoul... | [TouchRipple] Buggy interaction with draggable HTML attribute
<!--- Provide a general summary of the issue in the Title above -->
When the "draggable" HTML attribute is added to a component that has a TouchRipple, when subsequent drags occur that end inside of the TouchRipple area, the opacity will multiply.
![to... | Can you provide a minimal reproducible example? I would have expected this to be fixed in #16142 (v4.1.1)
Edit: I was able to reproduce it.
@joshwooding How do we reproduce? Is this a Windows platform thing?
@oliviertassinari https://codesandbox.io/s/f4pxl Click and drag a Tab multiple times fairly quickly
@joshwood... | 2019-06-15 16:22: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> root node should change the button component and add accessibility requirements', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> prop: disabled should forward it to native buttons', 'packages/material-ui/src/ButtonBase/But... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> ripple interactions should stop the ripple when dragging has finished'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ButtonBase/ButtonBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,252 | mui__material-ui-16252 | ['16151'] | 564aed388329ad75da7b1f5850e0a3bf24f25e56 | diff --git a/packages/material-ui-lab/src/Slider/Slider.js b/packages/material-ui-lab/src/Slider/Slider.js
--- a/packages/material-ui-lab/src/Slider/Slider.js
+++ b/packages/material-ui-lab/src/Slider/Slider.js
@@ -67,8 +67,15 @@ function percentToValue(percent, min, max) {
return (max - min) * percent + min;
}
+... | diff --git a/packages/material-ui-lab/src/Slider/Slider.test.js b/packages/material-ui-lab/src/Slider/Slider.test.js
--- a/packages/material-ui-lab/src/Slider/Slider.test.js
+++ b/packages/material-ui-lab/src/Slider/Slider.test.js
@@ -265,6 +265,13 @@ describe('<Slider />', () => {
thumb.simulate('keydown', move... | Slider stepValue < 1 gives rounding errors
<!-- Checked checkbox should look like this: [x] -->
- [x ] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x ] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
##... | This is due to the way javascript [stores decimal numbers](https://modernweb.com/what-every-javascript-developer-should-know-about-floating-points/)
If you go to your console right now and type 1.1 * 0.1 it will print 0.11000000000000001.
To get around this you can change the slider `valueReducer` passing a custo... | 2019-06-15 18:25:45+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> markActive state should set the mark active', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> Material-UI component API ref attaches the ref', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> when mouse leaves window should ... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> keyboard should round value to step precision'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Slider/Slider.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui-lab/src/Slider/Slider.js->program->function_declaration:roundValueToStep", "packages/material-ui-lab/src/Slider/Slider.js->program->function_declaration:ensurePrecision"] |
mui/material-ui | 16,275 | mui__material-ui-16275 | ['16247'] | 93f5b33392af2da5365bb53b97550ac68d795329 | diff --git a/docs/src/pages/components/slider/DiscreteSlider.js b/docs/src/pages/components/slider/DiscreteSlider.js
--- a/docs/src/pages/components/slider/DiscreteSlider.js
+++ b/docs/src/pages/components/slider/DiscreteSlider.js
@@ -48,12 +48,14 @@ export default function DiscreteSlider() {
Temperature
... | diff --git a/packages/material-ui-lab/src/Slider/Slider.test.js b/packages/material-ui-lab/src/Slider/Slider.test.js
--- a/packages/material-ui-lab/src/Slider/Slider.test.js
+++ b/packages/material-ui-lab/src/Slider/Slider.test.js
@@ -53,17 +53,6 @@ describe('<Slider />', () => {
return wrapper.find('[role="slider... | Slider mark formatting not honouring change to min/max values
When changing the default min/max values on a slider, the mark formatting stops working and appears to work based on default values.
https://codesandbox.io/s/material-demo-mg72p
| @Ajaay Can you explain explicitly in a bit more detail what the issue is? The issue template helps with this e.g. observed behaviour and expected behaviour
Hi Josh,
If you check the code sandbox and slide the slider, you’ll see that the marks are not formatting at the correct points.
Thanks
@Ajaay Your issue has ... | 2019-06-18 09:37: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> Material-UI component API ref attaches the ref', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> keyboard should round value to step precision', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> when mouse leaves window shoul... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> markActive state sets the marks active that are `within` the value', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> markActive state uses closed intervals for the within check'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Slider/Slider.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/components/slider/DiscreteSlider.js->program->function_declaration:DiscreteSlider"] |
mui/material-ui | 16,281 | mui__material-ui-16281 | ['16219'] | a7d25a25dac786a7bb9c5b1eab1605502d75404d | diff --git a/packages/material-ui/src/Slide/Slide.js b/packages/material-ui/src/Slide/Slide.js
--- a/packages/material-ui/src/Slide/Slide.js
+++ b/packages/material-ui/src/Slide/Slide.js
@@ -13,7 +13,7 @@ const GUTTER = 24;
// Translate the node so he can't be seen on the screen.
// Later, we gonna translate back t... | diff --git a/packages/material-ui/src/Slide/Slide.test.js b/packages/material-ui/src/Slide/Slide.test.js
--- a/packages/material-ui/src/Slide/Slide.test.js
+++ b/packages/material-ui/src/Slide/Slide.test.js
@@ -104,7 +104,7 @@ describe('<Slide />', () => {
describe('handleEntering()', () => {
it('shou... | change slide 'in' transform styles to none
<!--- Provide a general summary of the issue in the Title above -->
i was creating a drawer with a drag and drop package [(rbd from Atlassian)](https://github.com/atlassian/react-beautiful-dnd) when I stumbled upon an issue. due to the drawer being fixed to the right, the dra... | @gijsbotje Could it be a bug with react-beautiful-dnd? The transition is broken in https://codesandbox.io/s/ij7ux.
@oliviertassinari i mentioned below the button in that demo it is broken 😄
I could try and destruct the drawer and make another demo, though a PR might be the easier way of showing it.
Though the anima... | 2019-06-18 19:21:34+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Slide/Slide.test.js-><Slide /> transform styling handleExiting() should set element transform and transition in the `down` direction', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> transform styling handleEnter() should set element transform and transition in the `right` direction'... | ['packages/material-ui/src/Slide/Slide.test.js-><Slide /> transition lifecycle in handleEntering() should reset the translate3d', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> resize should take existing transform into account', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> transform styling handl... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Slide/Slide.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Slide/Slide.js->program->function_declaration:getTranslateValue"] |
mui/material-ui | 16,296 | mui__material-ui-16296 | ['16270'] | 5ce2141746722d730d09902fa9553c004d9fe7af | diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/packages/material-ui/src/Select/SelectInput.js
@@ -27,7 +27,7 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) {
disabled,
... | diff --git a/packages/material-ui/src/Select/SelectInput.test.js b/packages/material-ui/src/Select/SelectInput.test.js
--- a/packages/material-ui/src/Select/SelectInput.test.js
+++ b/packages/material-ui/src/Select/SelectInput.test.js
@@ -419,6 +419,12 @@ describe('<SelectInput />', () => {
});
});
+ it('sho... | [Select] node is undefined
<!-- Checked checkbox should look like this: [x] -->
- [ x ] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [ x ] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Expected Beha... | @ffjanhoeck Thanks for the report. This looks like a regression to me. What do you think of this fix?
```diff
diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
index 6ea5b3959..5c8cedd24 100644
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/pac... | 2019-06-19 18:22: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ["packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed ArrowUp key on select", "packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed key on select", 'packages/material-ui/src/Select/SelectInput.... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> should be able to return the input node via a ref object'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,298 | mui__material-ui-16298 | ['16241', '16241'] | ac392058af280e2247b6e5d4ca702d72839c4695 | diff --git a/packages/material-ui/src/InputBase/Textarea.js b/packages/material-ui/src/InputBase/Textarea.js
--- a/packages/material-ui/src/InputBase/Textarea.js
+++ b/packages/material-ui/src/InputBase/Textarea.js
@@ -76,7 +76,7 @@ const Textarea = React.forwardRef(function Textarea(props, ref) {
setState(prevSta... | diff --git a/packages/material-ui/src/InputBase/Textarea.test.js b/packages/material-ui/src/InputBase/Textarea.test.js
--- a/packages/material-ui/src/InputBase/Textarea.test.js
+++ b/packages/material-ui/src/InputBase/Textarea.test.js
@@ -177,5 +177,23 @@ describe('<Textarea />', () => {
wrapper.update();
... | [Textarea] Does not respond to rowsMax prop changes
As the title suggests, changing the rowsMax prop of a mounted TextField does nothing: the height of the textarea remains unchanged.
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] ... | Nice find. Looks like we need to change the threshold check to include the outer height e.g.
```diff
diff --git a/packages/material-ui/src/InputBase/Textarea.js b/packages/material-ui/src/InputBase/Textarea.js
index 519648805..1d896dab5 100644
--- a/packages/material-ui/src/InputBase/Textarea.js
+++ b/packages/m... | 2019-06-19 20:07:14+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout should take the padding into account with content-box', 'packages/material-ui/src/InputBase/Textarea.test.js->... | ['packages/material-ui/src/InputBase/Textarea.test.js-><Textarea /> layout should update its height when the "rowsMax" prop changes'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputBase/Textarea.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,397 | mui__material-ui-16397 | ['15512'] | c78b343ad2c673bd6c03918b3cc2dcb11f52ed1e | diff --git a/docs/src/modules/components/Link.js b/docs/src/modules/components/Link.js
--- a/docs/src/modules/components/Link.js
+++ b/docs/src/modules/components/Link.js
@@ -32,6 +32,7 @@ function Link(props) {
className: classNameProps,
innerRef,
naked,
+ role: roleProp,
router,
userLangua... | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.test.js b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.test.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
@@ -104,15 +104,16 @@ describe('<ButtonBase />', () => {
expect(bu... | [ButtonBase] Improve Button accessibility
Revert #10339 removed safeguard and add additional one so anchors missing href's are treated as buttons.
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
... | @bluSCALE4 Do you have a specific fix in mind? I think that we can apply the following but it won't help your case:
```diff
--- a/packages/material-ui/src/ButtonBase/ButtonBase.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.js
@@ -287,7 +287,10 @@ class ButtonBase extends React.Component {
buttonPr... | 2019-06-27 13:17:37+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> root node should change the button component and add accessibility requirements', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> prop: disabled should forward it to native buttons', 'packages/material-ui/src/ButtonBase/But... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> root node should automatically change the button to an anchor element when href is provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ButtonBase/ButtonBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/modules/components/Link.js->program->function_declaration:Link"] |
mui/material-ui | 16,399 | mui__material-ui-16399 | ['16037'] | 783b6934632714a844b7d440e6d05729f9f2dc0c | diff --git a/docs/src/modules/utils/parseMarkdown.js b/docs/src/modules/utils/parseMarkdown.js
--- a/docs/src/modules/utils/parseMarkdown.js
+++ b/docs/src/modules/utils/parseMarkdown.js
@@ -37,7 +37,7 @@ export const demoRegexp = /^"demo": "(.*)"/;
export function getContents(markdown) {
return markdown
.repl... | diff --git a/docs/src/modules/utils/parseMarkdown.test.js b/docs/src/modules/utils/parseMarkdown.test.js
new file mode 100644
--- /dev/null
+++ b/docs/src/modules/utils/parseMarkdown.test.js
@@ -0,0 +1,26 @@
+import { expect } from 'chai';
+import { getContents } from './parseMarkdown';
+
+describe('parseMarkdown', () ... | How to use react-stripe-js?
When changing any Stripe input the InputBase.js produces an error in the dirtyCheck when trying to access the value of either the inputRef.current or target.value: `Cannot read property 'value' of undefined`
<!--
Thank you very much for contributing to Material-UI by creating an issu... | @gvetsa Thanks for the report. It seems https://gist.github.com/lfalke/1c5e7168424c8b2a65dcfba425fcc310 is no longer working. This Stripe React element doesn't play very nicely with the idiomatic React APIs, they have no ref forwarding logic nor a standard event API. I would propose the following fix:
```diff
diff --... | 2019-06-27 15:33:05+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> with FormControl propagates filled state when uncontrolled', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent should inject onBlur and onFocus', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBas... | ['docs/src/modules/utils/parseMarkdown.test.js->parseMarkdown getContents Split markdown into an array, separating demos ignores possible code', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent errors throws on change if the target isnt mocked'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputBase/InputBase.test.js docs/src/modules/utils/parseMarkdown.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/modules/utils/parseMarkdown.js->program->function_declaration:getContents"] |
mui/material-ui | 16,401 | mui__material-ui-16401 | ['16270'] | c78b343ad2c673bd6c03918b3cc2dcb11f52ed1e | diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/packages/material-ui/src/Select/SelectInput.js
@@ -55,8 +55,7 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) {
const [menuM... | diff --git a/packages/material-ui/src/Select/SelectInput.test.js b/packages/material-ui/src/Select/SelectInput.test.js
--- a/packages/material-ui/src/Select/SelectInput.test.js
+++ b/packages/material-ui/src/Select/SelectInput.test.js
@@ -421,7 +421,11 @@ describe('<SelectInput />', () => {
it('should be able to r... | [Select] node is undefined
<!-- Checked checkbox should look like this: [x] -->
- [ x ] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [ x ] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Expected Beha... | @ffjanhoeck Thanks for the report. This looks like a regression to me. What do you think of this fix?
```diff
diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
index 6ea5b3959..5c8cedd24 100644
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/pac... | 2019-06-27 16:16:21+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ["packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed ArrowUp key on select", "packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed key on select", 'packages/material-ui/src/Select/SelectInput.... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> should be able to return the input node via a ref object'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,450 | mui__material-ui-16450 | ['16444'] | 7fb9b403553bb9d74f1ef00c07f53e61341cc71e | diff --git a/packages/material-ui/src/Menu/Menu.js b/packages/material-ui/src/Menu/Menu.js
--- a/packages/material-ui/src/Menu/Menu.js
+++ b/packages/material-ui/src/Menu/Menu.js
@@ -53,7 +53,7 @@ const Menu = React.forwardRef(function Menu(props, ref) {
...other
} = props;
- const autoFocus = autoFocusProp ... | diff --git a/packages/material-ui/test/integration/Menu.test.js b/packages/material-ui/test/integration/Menu.test.js
--- a/packages/material-ui/test/integration/Menu.test.js
+++ b/packages/material-ui/test/integration/Menu.test.js
@@ -1,5 +1,5 @@
import React from 'react';
-import { assert } from 'chai';
+import { ass... | Menu keyboard navigation broken in demos
<!--- Provide a general summary of the issue in the Title above -->
In #15901, the Menu demos were changed to use the `keepMounted` property. This breaks the auto-focus functionality in `MenuList` since it is then mounted before it is open and the `focus` call happens on mount.... | The PR that added keepMounted includes a rationale for it. But even if not it's still a documented prop and the component should support it. I want to revisit the keyboard navigation soon but we have other priorities that come first (see roadmap)
Ah, I found it:
> * aria-controls (was aria-owns) pointing to elements... | 2019-07-02 11:16:12+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/test/integration/Menu.test.js-><Menu> integration Using mount mounted open should change focus to the first item when down arrow is pressed', 'packages/material-ui/test/integration/Menu.test.js-><Menu> integration Using mount closing should close the menu with tab', 'packages/material-ui/test/int... | ['packages/material-ui/test/integration/Menu.test.js-><Menu> integration Using RTL render with keepMounted should focus the list on open'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/Menu.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,467 | mui__material-ui-16467 | ['11865'] | 73e995020a0949c2ad30204156712aeffc94a997 | diff --git a/packages/material-ui/src/FormControl/FormControlContext.d.ts b/packages/material-ui/src/FormControl/FormControlContext.d.ts
--- a/packages/material-ui/src/FormControl/FormControlContext.d.ts
+++ b/packages/material-ui/src/FormControl/FormControlContext.d.ts
@@ -1,9 +1,12 @@
import { Context } from 'react'... | diff --git a/packages/material-ui/src/FormControl/FormControl.test.js b/packages/material-ui/src/FormControl/FormControl.test.js
--- a/packages/material-ui/src/FormControl/FormControl.test.js
+++ b/packages/material-ui/src/FormControl/FormControl.test.js
@@ -7,7 +7,7 @@ import { act, cleanup, createClientRender } from ... | [FormControl] Expose the form control state
How does one get the Context managed by a `<FormControl/>` into one's own component that is intended to be a child of the `<FormControl/>`. The form control does not seem to pass disabled, focused, error as properties and also does not use React's new context API. Could you a... | @serle You can't. It's an implementation detail.
@oliviertassinari If the purpose of the FormControl is to act as the source of filled, focused, error states and then we should be able to use it as a building block for our own controls. It would be great if it could pass these as props to its direct children as well a... | 2019-07-03 15:16: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputProps should be able to get a ref', 'packages/material-ui/src/FormControl/FormControl.test.js-><FormControl /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/FormControl/FormControl.test.j... | ['packages/material-ui/src/FormControl/FormControl.test.js-><FormControl /> initial state should not be filled initially', 'packages/material-ui/src/FormControl/FormControl.test.js-><FormControl /> initial state should not be focused initially', 'packages/material-ui/src/FormControl/FormControl.test.js-><FormControl />... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/FormControl/FormControl.test.js packages/material-ui/src/InputBase/InputBase.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/FormControl/FormControlContext.js->program->function_declaration:useFormControl"] |
mui/material-ui | 16,585 | mui__material-ui-16585 | ['16584'] | 6d85b4b9d742959eed7907ef6f0e7e50233db60e | diff --git a/packages/material-ui/src/Modal/TrapFocus.js b/packages/material-ui/src/Modal/TrapFocus.js
--- a/packages/material-ui/src/Modal/TrapFocus.js
+++ b/packages/material-ui/src/Modal/TrapFocus.js
@@ -100,7 +100,18 @@ function TrapFocus(props) {
doc.addEventListener('focus', contain, true);
doc.addEvent... | diff --git a/packages/material-ui/src/Modal/Modal.test.js b/packages/material-ui/src/Modal/Modal.test.js
--- a/packages/material-ui/src/Modal/Modal.test.js
+++ b/packages/material-ui/src/Modal/Modal.test.js
@@ -1,8 +1,9 @@
import React from 'react';
import { assert, expect } from 'chai';
-import { spy } from 'sinon';... | [Modal] focus-trap fails when a focused element in the modal unmounts
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Expected Behavior 🤔
The di... | I'd say the actual issue is that focus isn't trapped inside the dialog. Intuitively we could return focus from document.body to the focus trap to catch this specific issue. We "just" need to research event order and transition of document.activeElement. Something like "if any blur event is fired return to focus to focu... | 2019-07-12 10:48:40+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Popover/Popover.test.js-><Popover /> paper should have a elevation prop passed down', "packages/material-ui/src/Popover/Popover.test.js-><Popover /> root node getOffsetTop should return rect.height if vertical is 'bottom'", 'packages/material-ui/src/Popover/Popover.test.js-><Popover /> positi... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> focus contains the focus if the active element is removed'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popover/Popover.test.js packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Modal/TrapFocus.js->program->function_declaration:TrapFocus"] |
mui/material-ui | 16,597 | mui__material-ui-16597 | ['16595'] | b6182ce67251bc965319ab8e48d2d2cf5f346b72 | diff --git a/docs/pages/api/modal.md b/docs/pages/api/modal.md
--- a/docs/pages/api/modal.md
+++ b/docs/pages/api/modal.md
@@ -44,7 +44,7 @@ This component shares many concepts with [react-overlays](https://react-bootstra
| <span class="prop-name">onBackdropClick</span> | <span class="prop-type">func</span> | | Callb... | diff --git a/packages/material-ui/src/Portal/Portal.test.js b/packages/material-ui/src/Portal/Portal.test.js
--- a/packages/material-ui/src/Portal/Portal.test.js
+++ b/packages/material-ui/src/Portal/Portal.test.js
@@ -47,21 +47,48 @@ describe('<Portal />', () => {
});
});
- it('should have access to the mou... | Portal: onRendered doesn't make sense if disablePortal is true
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not ... | null | 2019-07-14 09:38: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Portal/Portal.test.js-><Portal /> should call onRendered after child componentDidUpdate', 'packages/material-ui/src/Portal/Portal.test.js-><Portal /> server-side render nothing on the server', 'packages/material-ui/src/Portal/Portal.test.js-><Portal /> should render overlay into container (do... | ['packages/material-ui/src/Portal/Portal.test.js-><Portal /> ref should have access to the mountNode when disabledPortal={false}'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Portal/Portal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,628 | mui__material-ui-16628 | ['16697'] | 35d1c4aadf1865365b00c198453a5398c72cc39e | diff --git a/docs/pages/api/tabs.md b/docs/pages/api/tabs.md
--- a/docs/pages/api/tabs.md
+++ b/docs/pages/api/tabs.md
@@ -25,9 +25,10 @@ import Tabs from '@material-ui/core/Tabs';
| <span class="prop-name">component</span> | <span class="prop-type">elementType</span> | <span class="prop-default">'div'</span> | The co... | diff --git a/packages/material-ui/src/Tabs/TabIndicator.test.js b/packages/material-ui/src/Tabs/TabIndicator.test.js
--- a/packages/material-ui/src/Tabs/TabIndicator.test.js
+++ b/packages/material-ui/src/Tabs/TabIndicator.test.js
@@ -6,29 +6,34 @@ import TabIndicator from './TabIndicator';
describe('<TabIndicator />'... | TabIndicatorProps is useless
<!--- Provide a general summary of the issue in the Title above -->
I am trying to restyle Tabs and Tabs indicator component. What I wanted to achieve is to make tab indicator smaller (80%). Is surprised me this is not possible in your current implementation. Documentation (https://mater... | null | 2019-07-18 06:27:32+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: value indicator should render the indicator', 'packages/material-ui/src/Tabs/TabScrollButton.test.js-><TabScrollButton /> prop: direction should render with the left icon', 'packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: centered should render wit... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: orientation should support orientation="vertical"'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tabs/TabIndicator.test.js packages/material-ui/src/Tabs/TabScrollButton.test.js packages/material-ui/src/Tabs/Tabs.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,635 | mui__material-ui-16635 | ['16616'] | 2c5d99ed877b7710d09afbef4cb358c1c3cd4c80 | diff --git a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
--- a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
+++ b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
@@ -47,15 +47,14 @@ const TextareaAutosize = ... | diff --git a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js
--- a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js
+++ b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js
@@ -5,11 +5,11 @@ import ... | TextareaAutosize infinite render loop
I think the infinite render loop bug in #16387, #10717, #16222 may still exist in the new `TextareaAutosize` component, which is possibly related to Chrome in Win10 when scaled to 125% displaying a scrollbar.
### [CodeSandbox Demo ](https://codesandbox.io/s/boring-ride-9h9vx)
... | @ZYinMD I think that I have found the source of the issue. We compare inner height with outer height to determine if the hidden style should be applied. The issue is that these two values are not always in the same referential. They are not with a padding value and box sizing = content box. Can you confirm that this di... | 2019-07-18 12:54: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout should update its height when the "rowsMax" prop changes', 'packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout resize should handle the resize event', 'packages/material-ui/src/... | ['packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout should take the padding into account with content-box', 'packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout should take the border into account with border-box'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,694 | mui__material-ui-16694 | ['12831'] | 4d8206d3d44580345141405e5f78cd02fbb7ef99 | diff --git a/packages/material-ui/src/Modal/Modal.js b/packages/material-ui/src/Modal/Modal.js
--- a/packages/material-ui/src/Modal/Modal.js
+++ b/packages/material-ui/src/Modal/Modal.js
@@ -85,7 +85,7 @@ const Modal = React.forwardRef(function Modal(props, ref) {
} = props;
const theme = useTheme();
- const [... | diff --git a/packages/material-ui/src/Modal/Modal.test.js b/packages/material-ui/src/Modal/Modal.test.js
--- a/packages/material-ui/src/Modal/Modal.test.js
+++ b/packages/material-ui/src/Modal/Modal.test.js
@@ -144,6 +144,27 @@ describe('<Modal />', () => {
backdropSpan.simulate('click');
assert.strictEqu... | Dialog backdrop is persisted when initialized as open but then immediately closed
This should not be a duplicate of the transition issue as I'm not using a Transition, this is a default Dialog component (reproduced below using the Component API Demo page).
Essentially I think flipping the `open` prop too quickly res... | After you set open to false it does not set exited property of modal to true. So hidden class does not applied and dialog covers all area. Am I right? @kamranayub
I think that `handleExit` could not be called by a reason that i don't know after `getDerivedStateFromProps`.
I could be related with `getHasTransition`... | 2019-07-23 06:27:45+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should attach a handler to the backd... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should unmount the children when starting open and closing immediately'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,807 | mui__material-ui-16807 | ['16800'] | 7c325b0d8ff354261009cb90fb48aa1f4f662dd1 | diff --git a/packages/material-ui/src/Popper/Popper.js b/packages/material-ui/src/Popper/Popper.js
--- a/packages/material-ui/src/Popper/Popper.js
+++ b/packages/material-ui/src/Popper/Popper.js
@@ -61,8 +61,8 @@ const Popper = React.forwardRef(function Popper(props, ref) {
const ownRef = useForkRef(tooltipRef, ref)... | diff --git a/packages/material-ui/src/Popper/Popper.test.js b/packages/material-ui/src/Popper/Popper.test.js
--- a/packages/material-ui/src/Popper/Popper.test.js
+++ b/packages/material-ui/src/Popper/Popper.test.js
@@ -222,6 +222,32 @@ describe('<Popper />', () => {
});
});
+ describe('prop: disablePortal', ... | [Popper] TypeError: handlePopperRefRef.current is not a function
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue.... | I would propose the following fix:
```diff
diff --git a/packages/material-ui/src/Popper/Popper.js b/packages/material-ui/src/Popper/Popper.js
index 150fc169a..1471e127a 100644
--- a/packages/material-ui/src/Popper/Popper.js
+++ b/packages/material-ui/src/Popper/Popper.js
@@ -61,8 +61,8 @@ const Popper = React.for... | 2019-07-30 10:23: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip top-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip bottom-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> Ma... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: disablePortal should work', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: disablePortal sets preventOverflow to window when disablePortal is false'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popper/Popper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 16,850 | mui__material-ui-16850 | ['13922'] | e3144c52bc2f215c8dddb4d65ef6bcd9f5980b66 | diff --git a/docs/pages/api/modal.md b/docs/pages/api/modal.md
--- a/docs/pages/api/modal.md
+++ b/docs/pages/api/modal.md
@@ -39,6 +39,7 @@ This component shares many concepts with [react-overlays](https://react-bootstra
| <span class="prop-name">disableEscapeKeyDown</span> | <span class="prop-type">bool</span> | <sp... | diff --git a/packages/material-ui/src/Modal/Modal.test.js b/packages/material-ui/src/Modal/Modal.test.js
--- a/packages/material-ui/src/Modal/Modal.test.js
+++ b/packages/material-ui/src/Modal/Modal.test.js
@@ -804,4 +804,15 @@ describe('<Modal />', () => {
mount(<TestCase />);
});
});
+
+ describe('pro... | [Modal] Implement disableScrollLock property
Is there any documentation regarding this functionality out there? I saw a mention of it in the modal api reference but can't find when/how to use it.
| @fltonii We have no documentation about it as we are speaking. I'm not sure it's something that is worth mentioning in the API page of the modal. The only "valid" use case I have seen so far is around people bundling two versions of Material-UI, realizing that their modal logic isn't valid (as it can only have one top ... | 2019-08-01 17:02:58+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Modal/ModalManager.test.js->ModalManager should add a modal only once', 'pac... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: disablePortal should render the content into the parent'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Modal/ModalManager.test.js packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 8 | 0 | 8 | false | false | ["packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:handleNewContainer", "packages/material-ui/src/Modal/ModalManager.js->program->class_declaration:ModalManager->method_definition:constructor", "packages/material-ui/src/Modal/TrapFocus.js->program->function_declaration:TrapFocus", "docs/src... |
mui/material-ui | 16,882 | mui__material-ui-16882 | ['16475'] | 14e595fb18f781d2f49c83f85b006d86111ae328 | diff --git a/packages/material-ui-styles/src/styled/styled.js b/packages/material-ui-styles/src/styled/styled.js
--- a/packages/material-ui-styles/src/styled/styled.js
+++ b/packages/material-ui-styles/src/styled/styled.js
@@ -80,17 +80,18 @@ function styled(Component) {
const classes = useStyles(props);
... | diff --git a/packages/material-ui-styles/src/styled/styled.test.js b/packages/material-ui-styles/src/styled/styled.test.js
--- a/packages/material-ui-styles/src/styled/styled.test.js
+++ b/packages/material-ui-styles/src/styled/styled.test.js
@@ -45,12 +45,21 @@ describe('styled', () => {
});
describe('prop: cl... | Box clone ignores SyntheticEvent
Adding clone property to Box component will cause SyntheticEvent to break. It's actually passing styling props and nothing more.
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) ... | @fafamx So far, we have been spreading the props when using the cloneElement API in the codebase. Doing the same in this case sounds reasonable. We would need to change the spread logic around those lines: https://github.com/mui-org/material-ui/blob/143124dc944f61c9f4456ea3cd7e4a3e6cebd668/packages/material-ui-styles/s... | 2019-08-04 12:53:26+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-styles/src/styled/styled.test.js->styled should work as expected', 'packages/material-ui-styles/src/styled/styled.test.js->styled warnings warns if it cant detect the secondary action properly', 'packages/material-ui-styles/src/styled/styled.test.js->styled prop: clone should be able to clone the... | ['packages/material-ui-styles/src/styled/styled.test.js->styled prop: clone should be able to pass props to cloned element'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-styles/src/styled/styled.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-styles/src/styled/styled.js->program->function_declaration:styled"] |
mui/material-ui | 17,005 | mui__material-ui-17005 | ['11910'] | 10ed7cfb308de1d978886c13ac5a7c31700f7068 | diff --git a/packages/material-ui/src/Grid/Grid.js b/packages/material-ui/src/Grid/Grid.js
--- a/packages/material-ui/src/Grid/Grid.js
+++ b/packages/material-ui/src/Grid/Grid.js
@@ -64,6 +64,11 @@ function generateGrid(globalStyles, theme, breakpoint) {
}
}
+function getOffset(val, div = 1) {
+ const parse = pa... | diff --git a/packages/material-ui/src/Grid/Grid.test.js b/packages/material-ui/src/Grid/Grid.test.js
--- a/packages/material-ui/src/Grid/Grid.test.js
+++ b/packages/material-ui/src/Grid/Grid.test.js
@@ -1,8 +1,9 @@
import React from 'react';
-import { assert } from 'chai';
+import { assert, expect } from 'chai';
impo... | [Grid] Replace px to rem in spacing prop
Now
```jsx
<Grid spacing={8/padding: 4px|16/padding: 8px|32/padding: 16px|40/padding: 32px}>
```
Need
```jsx
<Grid spacing={8/padding:0.25rem|16/padding:0.5rem|32/padding:0.75rem|40/padding:1rem}>
```
or add another prop spacingRem
| @udanpe The Grid component aims to be as simple as possible. You don't have to use the spacing property, you can keep it to 0 and use rem on your side.
I changed the spacing function to output a `rem` string as per the 'bootstrap strategy' example(https://material-ui.com/customization/spacing/). However, this breaks th... | 2019-08-14 22:07:38+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Grid/Grid.test.js-><Grid /> prop: xs should apply the flex-grow class', 'packages/material-ui/src/Grid/Grid.test.js-><Grid /> prop: alignItems should apply the align-item class', 'packages/material-ui/src/Grid/Grid.test.js-><Grid /> Material-UI component API should render without errors in Re... | ['packages/material-ui/src/Grid/Grid.test.js-><Grid /> gutter should generate the right values'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Grid/Grid.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Grid/Grid.js->program->function_declaration:getOffset", "packages/material-ui/src/Grid/Grid.js->program->function_declaration:generateGutter"] |
mui/material-ui | 17,013 | mui__material-ui-17013 | ['16939'] | 10ed7cfb308de1d978886c13ac5a7c31700f7068 | diff --git a/packages/material-ui-lab/src/Rating/Rating.js b/packages/material-ui-lab/src/Rating/Rating.js
--- a/packages/material-ui-lab/src/Rating/Rating.js
+++ b/packages/material-ui-lab/src/Rating/Rating.js
@@ -15,6 +15,16 @@ function clamp(value, min, max) {
return value;
}
+function getDecimalPrecision(num)... | diff --git a/packages/material-ui-lab/src/Rating/Rating.test.js b/packages/material-ui-lab/src/Rating/Rating.test.js
--- a/packages/material-ui-lab/src/Rating/Rating.test.js
+++ b/packages/material-ui-lab/src/Rating/Rating.test.js
@@ -10,6 +10,7 @@ describe('<Rating />', () => {
const render = createClientRender({ s... | @material-ui/lab/Rating - wrong rendering for value of 3.9 and precision of 0.2
Like the title says, when you have a precision of 0.2 and value of 3.9, there are only 3 starts filled instead of 4.
The following code:
```jsx
import React from 'react';
import Rating from '@material-ui/lab/Rating';
export defaul... | @neupsh Thank you for the report. You are right, I have designed/tested the component with two precisions values: 1 and 0.5. I haven't looked much at the 0.x variations. But it's definitely something worth supporting. We had to solve a similar issue in the past with the slider component. I believe that we can apply the... | 2019-08-15 15:22:09+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Rating/Rating.test.js-><Rating /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui-lab/src/Rating/Rating.test.js-><Rating /> Material-UI component API applies the className to the root component', 'packages/material-ui-lab/src/Rating/Rati... | ['packages/material-ui-lab/src/Rating/Rating.test.js-><Rating /> should round the value to the provided precision'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Rating/Rating.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui-lab/src/Rating/Rating.js->program->function_declaration:roundValueToPrecision", "packages/material-ui-lab/src/Rating/Rating.js->program->function_declaration:getDecimalPrecision"] |
mui/material-ui | 17,019 | mui__material-ui-17019 | ['16094'] | 490ca9b220d15109d50116389cc8971cc1450d1b | diff --git a/packages/material-ui-styles/src/getStylesCreator/getStylesCreator.js b/packages/material-ui-styles/src/getStylesCreator/getStylesCreator.js
--- a/packages/material-ui-styles/src/getStylesCreator/getStylesCreator.js
+++ b/packages/material-ui-styles/src/getStylesCreator/getStylesCreator.js
@@ -58,7 +58,6 @@... | diff --git a/packages/material-ui-styles/src/makeStyles/makeStyles.test.js b/packages/material-ui-styles/src/makeStyles/makeStyles.test.js
--- a/packages/material-ui-styles/src/makeStyles/makeStyles.test.js
+++ b/packages/material-ui-styles/src/makeStyles/makeStyles.test.js
@@ -211,7 +211,7 @@ describe('makeStyles', ()... | jss-rtl is not working when passing style as an object to makeStyles
Apparently 'jss-rtl' has no effect when passing styles as an object to the 'makeStyles', however, it does work when returning styles from a function.
<!-- Checked checkbox should look like this: [x] -->
- [x ] This is not a v0.x issue. <!-- (v0.x... | @Cyrus-d Thanks for the issue, this is the more updated version of #10823. You have the following workaround:
```jsx
<StylesProvider flip />
```
https://codesandbox.io/s/material-demo-oo8sg
Do you want to update the documentation about it :)?
@oliviertassinari thanks for the suggestion, but I am a bit confused n... | 2019-08-15 21:13: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-styles/src/makeStyles/makeStyles.test.js->makeStyles classname quality should use the displayName', 'packages/material-ui-styles/src/withStyles/withStyles.test.js->withStyles hoists mui internals', 'packages/material-ui-styles/src/withStyles/withStyles.test.js->withStyles integration should suppo... | ['packages/material-ui-styles/src/withStyles/withStyles.test.js->withStyles integration should run lifecycles with no theme', 'packages/material-ui-styles/src/makeStyles/makeStyles.test.js->makeStyles integration should run lifecycles with no theme'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-styles/src/withStyles/withStyles.test.js packages/material-ui-styles/src/makeStyles/makeStyles.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui-styles/src/getStylesCreator/getStylesCreator.js->program->function_declaration:getStylesCreator", "packages/material-ui-styles/src/makeStyles/makeStyles.js->program->function_declaration:makeStyles"] |
mui/material-ui | 17,115 | mui__material-ui-17115 | ['17084'] | 343ae8e196292cef96e53f08753c634c02dc6fd5 | diff --git a/packages/material-ui/src/Backdrop/Backdrop.js b/packages/material-ui/src/Backdrop/Backdrop.js
--- a/packages/material-ui/src/Backdrop/Backdrop.js
+++ b/packages/material-ui/src/Backdrop/Backdrop.js
@@ -9,6 +9,9 @@ export const styles = {
root: {
zIndex: -1,
position: 'fixed',
+ display: 'fl... | diff --git a/packages/material-ui/src/Backdrop/Backdrop.test.js b/packages/material-ui/src/Backdrop/Backdrop.test.js
--- a/packages/material-ui/src/Backdrop/Backdrop.test.js
+++ b/packages/material-ui/src/Backdrop/Backdrop.test.js
@@ -1,18 +1,16 @@
import React from 'react';
import { assert } from 'chai';
-import { c... | BackDrop component does not render children
<!-- Checked checkbox should look like this: [x] -->
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
... | > I'm trying to create a full screen loader with a backdrop and the loading indicator doesn't get rendered because the Backdrop component only renders the div.
@dominictwlee Interesting, I like the idea. What do you think of this diff?
```diff
diff --git a/packages/material-ui/src/Backdrop/Backdrop.js b/packages/m... | 2019-08-22 19:40:01+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Backdrop/Backdrop.test.js-><Backdrop /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/Backdrop/Backdrop.test.js-><Backdrop /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui/src/... | ['packages/material-ui/src/Backdrop/Backdrop.test.js-><Backdrop /> should render a backdrop div with content of nested children'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Backdrop/Backdrop.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,120 | mui__material-ui-17120 | ['17049'] | 343ae8e196292cef96e53f08753c634c02dc6fd5 | diff --git a/docs/src/modules/utils/helpers.js b/docs/src/modules/utils/helpers.js
--- a/docs/src/modules/utils/helpers.js
+++ b/docs/src/modules/utils/helpers.js
@@ -99,18 +99,18 @@ function getDependencies(raw, options = {}) {
jss: 'next',
'jss-plugin-template': 'next',
};
- const re = /^import\s.*\sfro... | diff --git a/docs/src/modules/utils/helpers.test.js b/docs/src/modules/utils/helpers.test.js
--- a/docs/src/modules/utils/helpers.test.js
+++ b/docs/src/modules/utils/helpers.test.js
@@ -31,7 +31,7 @@ const styles = theme => ({
});
it('should handle * dependencies', () => {
- const s2 = `
+ const source =... | [Minor] CodeSandbox Demos has dependency errors
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look li... | @Erkin97 Good catch. What do you think of these changes?
```diff
diff --git a/docs/src/modules/utils/helpers.js b/docs/src/modules/utils/helpers.js
index 8113a8815..4d60ac59f 100644
--- a/docs/src/modules/utils/helpers.js
+++ b/docs/src/modules/utils/helpers.js
@@ -99,18 +99,18 @@ function getDependencies(raw, op... | 2019-08-23 05:38:32+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['docs/src/modules/utils/helpers.test.js->docs getDependencies helpers should handle @ dependencies', 'docs/src/modules/utils/helpers.test.js->docs getDependencies helpers can collect required @types packages', 'docs/src/modules/utils/helpers.test.js->docs getDependencies helpers should support next dependencies', 'doc... | ['docs/src/modules/utils/helpers.test.js->docs getDependencies helpers should handle multilines'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha docs/src/modules/utils/helpers.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/modules/utils/helpers.js->program->function_declaration:getDependencies"] |
mui/material-ui | 17,139 | mui__material-ui-17139 | ['6625'] | 8ec0e6faf0dfebb6843adb4f684e35ae8274beef | diff --git a/docs/pages/api/table-cell.md b/docs/pages/api/table-cell.md
--- a/docs/pages/api/table-cell.md
+++ b/docs/pages/api/table-cell.md
@@ -56,6 +56,7 @@ Any other props supplied will be provided to the root element (native element).
| <span class="prop-name">alignCenter</span> | <span class="prop-name">MuiTabl... | diff --git a/packages/material-ui/src/Table/Table.test.js b/packages/material-ui/src/Table/Table.test.js
--- a/packages/material-ui/src/Table/Table.test.js
+++ b/packages/material-ui/src/Table/Table.test.js
@@ -70,6 +70,7 @@ describe('<Table />', () => {
expect(context).to.deep.equal({
size: 'medium',
... | [Table] Fixing head in material
<!-- Have a QUESTION? Please ask in [StackOverflow or gitter](http://tr.im/77pVj. -->
### For Fixing table Head in material 1.0.0 11 alpha
I have a table with scrolling rows but I am not able to fix the header.
Is there a property to do so as fixedHeader was in material 0.15 a... | I ran into the same issue today. Version 0.15 had the `fixedHeader` prop, v 1.x doesn't. I assume that there are plans to get this in.
Same problem with `Material-ui v1.0.0-beta.16`.
Would be really nice to have this feature back!
Same problem with Material-ui v1.0.0-beta.33
This is a must have feature! I think anyo... | 2019-08-24 21:27: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Table/Table.test.js-><Table /> prop: component can render a different component', 'packages/material-ui/src/Table/Table.test.js-><Table /> should render children', 'packages/material-ui/src/Table/Table.test.js-><Table /> Material-UI component API applies to root class to the root component if... | ['packages/material-ui/src/Table/Table.test.js-><Table /> should define table in the child context'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Table/Table.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,174 | mui__material-ui-17174 | ['17124'] | 837a3af5fcd9b24e537f9c775f5b1c9ee1a39bba | diff --git a/packages/material-ui/src/Tooltip/Tooltip.js b/packages/material-ui/src/Tooltip/Tooltip.js
--- a/packages/material-ui/src/Tooltip/Tooltip.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.js
@@ -261,14 +261,10 @@ function Tooltip(props) {
clearTimeout(enterTimer.current);
clearTimeout(leaveTimer... | diff --git a/packages/material-ui/src/Tooltip/Tooltip.test.js b/packages/material-ui/src/Tooltip/Tooltip.test.js
--- a/packages/material-ui/src/Tooltip/Tooltip.test.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.test.js
@@ -101,6 +101,8 @@ describe('<Tooltip />', () => {
children.simulate('mouseOver');
ass... | Tooltip is not working properly
On hovering next element showing the previously hovered element tooltip.
## Current Behavior 😯
Showing previous element tooltip
## Expected Behavior 🤔
... | @skirankumar7 Thanks for the report. What do you think of this fix?
```diff
diff --git a/packages/material-ui/src/Tooltip/Tooltip.js b/packages/material-ui/src/Tooltip/Tooltip.js
index bb716b431..ee2224c26 100644
--- a/packages/material-ui/src/Tooltip/Tooltip.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.js
@... | 2019-08-26 13:54:44+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: delay should take the enterDelay into account', 'packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: delay should take the leaveDelay into account', 'packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: overrides should... | ['packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: interactive should not animate twice'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip"] |
mui/material-ui | 17,240 | mui__material-ui-17240 | ['17231'] | 184bf1c6164ee5105fdb7a6bad2b2a0aa542eff6 | diff --git a/docs/pages/api/slider.md b/docs/pages/api/slider.md
--- a/docs/pages/api/slider.md
+++ b/docs/pages/api/slider.md
@@ -31,7 +31,8 @@ You can learn more about the difference by [reading our guide](/guides/minimizin
| <span class="prop-name">component</span> | <span class="prop-type">elementType</span> | <sp... | diff --git a/packages/material-ui/src/Slider/Slider.test.js b/packages/material-ui/src/Slider/Slider.test.js
--- a/packages/material-ui/src/Slider/Slider.test.js
+++ b/packages/material-ui/src/Slider/Slider.test.js
@@ -454,11 +454,36 @@ describe('<Slider />', () => {
PropTypes.resetWarningCache();
});
- ... | Slider: should be able to label each thumb with a different aria-label
<!-- Provide a general summary of the issue in the Title above -->
Slider's `aria-label` prop is a string, and that same string gets applied to all thumbs. Ideally it should also accept a string array, and apply each string to each thumb, similar t... | @city41 Thank you for the link toward w3.org. It does make sense, I believe that we can replicate the same strategy that we use with `aria-valuetext` (`getAriaValueText`).
> each string in the array should go to its corresponding thumb's aria-label
We have decided not to override existing native types to avoid confu... | 2019-08-30 16:22:21+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Slider/Slider.test.js-><Slider /> keyboard should reach right edge value', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> Material-UI component API shou... | ['packages/material-ui/src/Slider/Slider.test.js-><Slider /> should support getAriaLabel', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> warnings should warn if aria-label is provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Slider/Slider.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,299 | mui__material-ui-17299 | ['17294'] | 40fad153618b93c17726b35d110718a0929de5c6 | diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/packages/material-ui/src/Select/SelectInput.js
@@ -55,58 +55,49 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) {
} = props;... | diff --git a/packages/material-ui/src/Select/Select.test.js b/packages/material-ui/src/Select/Select.test.js
--- a/packages/material-ui/src/Select/Select.test.js
+++ b/packages/material-ui/src/Select/Select.test.js
@@ -88,13 +88,21 @@ describe('<Select />', () => {
expect(container.querySelector('input')).to.have.... | Can not blur Select component when it is controlled
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should loo... | https://github.com/mui-org/material-ui/blob/e0de07dfc90cacec1487a10b0ee7423b7de11e9d/packages/material-ui/src/Select/SelectInput.js#L108
It seems the blur was ignored even the menu was not opened.
Thank you for opening this issue and providing a reproduction.
It does seem like a bug since `onBlur` isn't called ei... | 2019-09-03 16:31: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/test/integration/Select.test.js-><Select> integration with label is displayed as focused while open', 'packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple select... | ['packages/material-ui/test/integration/Select.test.js-><Select> integration with label does not stays in an active state if an open action did not actually open'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/test/integration/Select.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,301 | mui__material-ui-17301 | ['10763'] | 0ddd56f5d389bfd19120d38fc4302f32f238be6f | diff --git a/docs/pages/api/speed-dial-action.md b/docs/pages/api/speed-dial-action.md
--- a/docs/pages/api/speed-dial-action.md
+++ b/docs/pages/api/speed-dial-action.md
@@ -24,16 +24,16 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| Name | Type | Default | Description |
|:--... | diff --git a/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js b/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js
--- a/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js
+++ b/packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js
@@ -7,6 +7,7 @@ import {
getClasses,
wrapsIntrinsicElement,... | [SpeedDial] SpeedDialAction visibility is poor on dark themes
<!--- Provide a general summary of the issue in the Title above -->
The icon and button colors on SpeedDialActions have weak visibility on dark themes. This can be seen on the material-ui site itself by switching to the dark theme and viewing the SpeedDial... | @ryanfields You're quite right. Would you like to try and improve it?
@mbrookes Started looking into a fix, but I need to spend time familiarizing myself with Material-UI's structure and inner workings. This is the first time I've tried working with the code. I will circle back to this in a couple weeks.
Thanks. Shou... | 2019-09-03 17:31:37+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/SpeedDialIcon/SpeedDialIcon.test.js-><SpeedDialIcon /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/SpeedDialIcon/SpeedDialIcon.test.js-><SpeedDialIcon /> should render the icon with the icon and iconOpen classe... | ['packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js-><SpeedDial /> dial focus actions navigation ignores array keys orthogonal to the direction', 'packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js-><SpeedDialAction /> should render the button with the fab class', 'packages/material-ui-lab/src/... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js test/regressions/tests/SpeedDial/Directions.js packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js packages/material-... | Refactoring | false | true | false | false | 5 | 0 | 5 | false | false | ["docs/src/pages/components/speed-dial/SpeedDialTooltipOpen.js->program->function_declaration:SpeedDialTooltipOpen", "docs/src/pages/components/speed-dial/OpenIconSpeedDial.js->program->function_declaration:OpenIconSpeedDial", "packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip", "packag... |
mui/material-ui | 17,304 | mui__material-ui-17304 | ['14203'] | b18a78e8cdad5894e96e65d6451545e075ed9d15 | diff --git a/docs/pages/api/select.md b/docs/pages/api/select.md
--- a/docs/pages/api/select.md
+++ b/docs/pages/api/select.md
@@ -29,8 +29,9 @@ You can learn more about the difference by [reading our guide](/guides/minimizin
| <span class="prop-name">classes</span> | <span class="prop-type">object</span> | | Overrid... | diff --git a/packages/material-ui/src/Select/Select.test.js b/packages/material-ui/src/Select/Select.test.js
--- a/packages/material-ui/src/Select/Select.test.js
+++ b/packages/material-ui/src/Select/Select.test.js
@@ -7,6 +7,8 @@ import MenuItem from '../MenuItem';
import Input from '../Input';
import Select from '.... | Select doesn't support variant="outlined"
So in the docs of `Select` component we can choose from either `standard`, `outlined` or `filled` variants
```
<Select variant='outlined' />
```
However by default adding `outlined` doesn't change a thing on the component visuall, except that it receives `outlined` class.... | Expected behavior because it is documented as such: https://material-ui.com/api/select/#props
The documentation also claims to spread props to `Input` which is only true for default behavior. Not when `input={<OtherElement />}` is used.
Sorry, I'm confused - how is that expected behavior? What does `variant='outline... | 2019-09-03 20:24:19+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Select/Select.test.js-><Select /> accessibility the listbox is focusable', 'packages/material-ui/src/Select/Select.test.js-><Select /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Select/Select.test.js-><Select /> accessibility sets aria-ex... | ['packages/material-ui/src/Select/Select.test.js-><Select /> prop: variant Should render a OutlinedInput'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/src/pages/components/selects/SimpleSelect.js->program->function_declaration:SimpleSelect", "docs/src/pages/components/selects/NativeSelects.js->program->function_declaration:NativeSelects"] |
mui/material-ui | 17,310 | mui__material-ui-17310 | ['17289'] | 310409e18961e1175bd79bbc8b9efceaab7e7f39 | diff --git a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
--- a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
+++ b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js
@@ -68,17 +68,18 @@ const TextareaAutosize = ... | diff --git a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js
--- a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js
+++ b/packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js
@@ -79,8 +79,8 @@ describ... | Multiline input doesn't have a scrollbar when passing rowsMax
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox ... | @rbhalla Thanks for the report, the mistake comes from ignoring state updates that should impact the render method. What do you think of this diff? Do you want to submit a pull request? :)
```diff
diff --git a/packages/material-ui/src/TextareaAutosize/TextareaAutosize.js b/packages/material-ui/src/TextareaAutosize/... | 2019-09-04 11:04:29+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout should update its height when the "rowsMax" prop changes', 'packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> Material-UI component API does spread props to the root component', 'pack... | ['packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout resize should handle the resize event', 'packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js-><TextareaAutosize /> layout should take the border into account with border-box', 'packages/material-ui/src/Texta... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TextareaAutosize/TextareaAutosize.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,337 | mui__material-ui-17337 | ['17333'] | 93e9ab602fb57eb340738065725e0b799a82142b | diff --git a/packages/material-ui/src/Modal/Modal.js b/packages/material-ui/src/Modal/Modal.js
--- a/packages/material-ui/src/Modal/Modal.js
+++ b/packages/material-ui/src/Modal/Modal.js
@@ -1,7 +1,7 @@
import React from 'react';
import ReactDOM from 'react-dom';
import PropTypes from 'prop-types';
-import { useThem... | diff --git a/packages/material-ui/src/Modal/Modal.test.js b/packages/material-ui/src/Modal/Modal.test.js
--- a/packages/material-ui/src/Modal/Modal.test.js
+++ b/packages/material-ui/src/Modal/Modal.test.js
@@ -4,7 +4,9 @@ import { useFakeTimers, spy } from 'sinon';
import PropTypes from 'prop-types';
import consoleE... | [Modal] No longer supports default props via theme
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look... | @ianschmitz This is related to #16442. We could easily restore the functionality. e.g.
https://github.com/mui-org/material-ui/blob/93e9ab602fb57eb340738065725e0b799a82142b/packages/material-ui/src/useMediaQuery/useMediaQuery.js#L10-L14
Sounds right. It wasn't clear in the migration docs that the removal of the classes... | 2019-09-06 00:50:38+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should attach a handler to the backd... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> props should consume theme default props'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,422 | mui__material-ui-17422 | ['17399'] | c6f9fabb9c9c5ed102dea254b048a361c4fd3a15 | diff --git a/packages/material-ui/src/ExpansionPanel/ExpansionPanel.js b/packages/material-ui/src/ExpansionPanel/ExpansionPanel.js
--- a/packages/material-ui/src/ExpansionPanel/ExpansionPanel.js
+++ b/packages/material-ui/src/ExpansionPanel/ExpansionPanel.js
@@ -96,6 +96,25 @@ const ExpansionPanel = React.forwardRef(fu... | diff --git a/packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js b/packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js
--- a/packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js
+++ b/packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js
@@ -38,7 +38,6 @@ describe('<ExpansionPan... | [core] Warn when changing between controlled and uncontrolled
<!-- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbo... | Is this up for grabs? I would like to contribute on this. 🙂
Yes, we would love to see your contribution :D. | 2019-09-14 06:42:12+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js-><ExpansionPanel /> prop: children should accept empty content', 'packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: delay should take the enterDelay into account', 'packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js-><Expansi... | ['packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> warnings should warn when switching between uncontrolled to controlled', 'packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js-><ExpansionPanel /> warnings should warn when switching from controlled to uncontrolled', 'packages/material-ui/src/Sli... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js packages/material-ui/src/Slider/Slider.test.js packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip"] |
mui/material-ui | 17,488 | mui__material-ui-17488 | ['17476'] | e48aebaade90cc45e09dd2364753ec663b62b727 | diff --git a/packages/material-ui-lab/src/TreeItem/TreeItem.js b/packages/material-ui-lab/src/TreeItem/TreeItem.js
--- a/packages/material-ui-lab/src/TreeItem/TreeItem.js
+++ b/packages/material-ui-lab/src/TreeItem/TreeItem.js
@@ -111,10 +111,10 @@ const TreeItem = React.forwardRef(function TreeItem(props, ref) {
... | diff --git a/packages/material-ui-lab/src/TreeItem/TreeItem.test.js b/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
--- a/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
+++ b/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
@@ -40,6 +40,52 @@ describe('<TreeItem />', () => {
expect(handleCli... | [TreeItem] Prop "endIcon" is not used
I try to use `endIcon` prop in `<TreeItem />` but it didn't work.
I checked the code of TreeItem.js and found `endIcon` prop is not being used:
```js
if (!icon) {
if (expandable) {
if (!expanded) {
icon = expandIcon || icons.defaultExpandIcon;
} e... | @Chocolatl Thank you for reporting this problem, your fix looks correct. Do you want to open a pull request with it? :)
```diff
diff --git a/packages/material-ui-lab/src/TreeItem/TreeItem.js b/packages/material-ui-lab/src/TreeItem/TreeItem.js
index 36466abb0..02841ef1b 100644
--- a/packages/material-ui-lab/src/Tr... | 2019-09-19 12:34:45+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> Accessibility when a tree receives focus should focus the selected node if a node is selected before the tree receives focus', "packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> Accessibility left arrow interaction should move foc... | ['packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> should display the right icons'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/TreeItem/TreeItem.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,506 | mui__material-ui-17506 | ['16644'] | 914b60648e5fc3f80cfcca35b4f82c11305f966b | diff --git a/docs/pages/api/menu.md b/docs/pages/api/menu.md
--- a/docs/pages/api/menu.md
+++ b/docs/pages/api/menu.md
@@ -25,10 +25,10 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| Name | Type | Default | Description |
|:-----|:-----|:--------|:------------|
| <span class="pr... | diff --git a/packages/material-ui/src/Menu/Menu.test.js b/packages/material-ui/src/Menu/Menu.test.js
--- a/packages/material-ui/src/Menu/Menu.test.js
+++ b/packages/material-ui/src/Menu/Menu.test.js
@@ -152,13 +152,12 @@ describe('<Menu />', () => {
it('should open during the initial mount', () => {
const wrapp... | Menu initial focus does not follow WAI-ARIA recommendations
This is a follow-up to discussion in #16294 with @eps1lon and @ianschmitz, but I didn't want to add this into a closed issue or merged pull request.
In @ianschmitz's comment [here](https://github.com/mui-org/material-ui/pull/16294#issuecomment-503731492), t... | Thanks for summarizing @ryancogswell.
> I, however, don't see value in adding the roving tabindex back in for Menu. As I understand it, the purpose of the roving tabindex is so that if you tab away from a composite widget (see #15597) and then shift+tab back to it, your focus location will be remembered. But for Men... | 2019-09-21 10:29:37+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Menu/Menu.test.js-><Menu /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Menu/Menu.test.js-><Menu /> should pass `classes.paper` to the Popover', 'packages/material-ui/src/Menu/Menu.test.js-><Menu /> event callbacks entering should fire cal... | ['packages/material-ui/test/integration/Menu.test.js-><Menu /> integration Menu variant differences [variant=menu] will focus the first item if nothing is selected', 'packages/material-ui/test/integration/Menu.test.js-><Menu /> integration Menu variant differences [variant=menu] prioritizes `autoFocus` on `MenuItem`', ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/Menu.test.js packages/material-ui/test/integration/NestedMenu.test.js packages/material-ui/src/Menu/Menu.test.js test/utils/initMatchers.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,571 | mui__material-ui-17571 | ['17539'] | f25c643ae320e0b4b194445bb4b0b5f06f206dfd | diff --git a/docs/pages/api/menu-list.md b/docs/pages/api/menu-list.md
--- a/docs/pages/api/menu-list.md
+++ b/docs/pages/api/menu-list.md
@@ -18,15 +18,20 @@ import { MenuList } from '@material-ui/core';
You can learn more about the difference by [reading this guide](/guides/minimizing-bundle-size/).
-
+A permane... | diff --git a/packages/material-ui/src/MenuList/MenuList.test.js b/packages/material-ui/src/MenuList/MenuList.test.js
--- a/packages/material-ui/src/MenuList/MenuList.test.js
+++ b/packages/material-ui/src/MenuList/MenuList.test.js
@@ -1,8 +1,9 @@
import React from 'react';
-import { assert } from 'chai';
+import { exp... | MenuList is not accessible
Creating this to track the follow-up fixes from #16644 for `MenuList`. #17506 solves the `Menu` focus issue which seems to work well, but we still need proper keyboard support in `MenuList`.
See #16644 for in-depth discussion on this issues.
| Tech | Version |
| ----------- | --... | Yep thanks for opening this. I want to move the keyboard navigation to menulist and menu only handles initial focus. Basically MenuList implements listbox and Menu is just a styled wrapper. | 2019-09-25 14:01: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation down arrow can go to all items while not changing tabIndex', 'packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation - preselec... | ['packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration initial focus is controlled by setting the selected prop when `autoFocusItem` is enabled', 'packages/material-ui/test/integration/MenuList.test.js-><MenuList> integration keyboard controls and tabIndex manipulation should select the secont... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/MenuList.test.js packages/material-ui/src/MenuList/MenuList.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/src/pages/components/menus/MenuListComposition.js->program->function_declaration:MenuListComposition", "docs/src/pages/components/menus/MenuListComposition.js->program->function_declaration:MenuListComposition->function_declaration:handleListKeyDown"] |
mui/material-ui | 17,600 | mui__material-ui-17600 | ['17494'] | 40fad153618b93c17726b35d110718a0929de5c6 | diff --git a/docs/pages/api/button.md b/docs/pages/api/button.md
--- a/docs/pages/api/button.md
+++ b/docs/pages/api/button.md
@@ -31,9 +31,11 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">disabled</span> | <span class="prop-type">bool</span> | <span clas... | diff --git a/packages/material-ui/src/Button/Button.test.js b/packages/material-ui/src/Button/Button.test.js
--- a/packages/material-ui/src/Button/Button.test.js
+++ b/packages/material-ui/src/Button/Button.test.js
@@ -267,6 +267,28 @@ describe('<Button />', () => {
expect(button).to.have.class(classes.containedSi... | [Button] Icon Button Spacing Uneven
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x]... | The button has 16px of padding to the left of the text portion of the label, and to the right of the icon, ~~which is correct per the spec.~~
I had wondered recently though whether we should support `start... | 2019-09-28 23:39:40+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Button/Button.test.js-><Button /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render an inherit outlined button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a large ou... | ['packages/material-ui/src/Button/Button.test.js-><Button /> should render a button with endIcon', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a button with startIcon'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Button/Button.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 3 | 0 | 3 | false | false | ["docs/src/pages/components/buttons/IconLabelButtons.js->program->function_declaration:IconLabelButtons", "docs/src/modules/components/MarkdownDocs.js->program->function_declaration:MarkdownDocs", "docs/src/modules/components/AppFrame.js->program->function_declaration:AppFrame"] |
mui/material-ui | 17,640 | mui__material-ui-17640 | ['17634'] | 05c533bd1f044593b772191066f25dd8b916ff5d | diff --git a/docs/pages/api/button.md b/docs/pages/api/button.md
--- a/docs/pages/api/button.md
+++ b/docs/pages/api/button.md
@@ -61,6 +61,12 @@ Any other props supplied will be provided to the root element ([ButtonBase](/api
| <span class="prop-name">focusVisible</span> | <span class="prop-name">Mui-focusVisible</sp... | diff --git a/packages/material-ui/src/Button/Button.test.js b/packages/material-ui/src/Button/Button.test.js
--- a/packages/material-ui/src/Button/Button.test.js
+++ b/packages/material-ui/src/Button/Button.test.js
@@ -40,8 +40,12 @@ describe('<Button />', () => {
expect(button).not.to.have.class(classes.contained... | Bigger horizontal padding for small size button
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Summary 💡
The padding of the small size button is : `4px 8px`. It doesn't look good to my eyes:
 but 12px would be good for me
@lcswillems Interesting concern, it seems that... | 2019-09-30 17:15:17+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Button/Button.test.js-><Button /> should render an inherit outlined button', 'packages/material-ui/src/ButtonGroup/ButtonGroup.test.js-><ButtonGroup /> can pass fullWidth to Button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a text secondary button', 'packages/... | ['packages/material-ui/src/Button/Button.test.js-><Button /> should render a large text button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a small outlined button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a small contained button', 'packages/material-ui/... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Button/Button.test.js packages/material-ui/src/ButtonGroup/ButtonGroup.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,661 | mui__material-ui-17661 | ['16260'] | 9a538bc0ce1fb865985822105d29bf7db6055fff | diff --git a/packages/material-ui-system/src/style.js b/packages/material-ui-system/src/style.js
--- a/packages/material-ui-system/src/style.js
+++ b/packages/material-ui-system/src/style.js
@@ -26,7 +26,7 @@ function style(options) {
if (typeof themeMapping === 'function') {
value = themeMapping(propVa... | diff --git a/packages/material-ui-system/src/style.test.js b/packages/material-ui-system/src/style.test.js
--- a/packages/material-ui-system/src/style.test.js
+++ b/packages/material-ui-system/src/style.test.js
@@ -81,6 +81,19 @@ describe('style', () => {
});
});
+ it('should fallback to value if theme value... | [Box] boxShadow property is not flowing through
<!--- Provide a general summary of the issue in the Title above -->
The `boxShadow` property of `Box` is not showing up in HTML.
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I ha... | Just looked at the examples. It appears that the `boxShadow` property is expected to be a number. I was looking at old type definitions that specified it as `React.CSSProperties`.
Would be nice to have a way to specify as a CSS string property.
@nareshbhatia Correct, this is a feature request, so far, the shadow sho... | 2019-10-02 08:05:12+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-system/src/style.test.js->style should transform the prop correctly', 'packages/material-ui-system/src/style.test.js->style should support array theme value', 'packages/material-ui-system/src/style.test.js->style should work', 'packages/material-ui-system/src/style.test.js->style should support b... | ['packages/material-ui-system/src/style.test.js->style should fallback to value if theme value is an array and index missing'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-system/src/style.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-system/src/style.js->program->function_declaration:style"] |
mui/material-ui | 17,680 | mui__material-ui-17680 | ['19213'] | d6fb08cb19b77d4faaa4e67c66fa0b063162e1ea | diff --git a/docs/pages/api/outlined-input.md b/docs/pages/api/outlined-input.md
--- a/docs/pages/api/outlined-input.md
+++ b/docs/pages/api/outlined-input.md
@@ -38,7 +38,8 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">inputComponent</span> | <span class... | diff --git a/packages/material-ui/src/TextField/TextField.test.js b/packages/material-ui/src/TextField/TextField.test.js
--- a/packages/material-ui/src/TextField/TextField.test.js
+++ b/packages/material-ui/src/TextField/TextField.test.js
@@ -92,9 +92,19 @@ describe('<TextField />', () => {
describe('with an outli... | [Autocomplete] Adding startAdornment results in extra top padding on IE11 only
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
Using a `startAdor... | null | 2019-10-03 10:21:18+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> structure should forward the fullWidth prop to Input', 'packages/material-ui/src/TextField/TextField.test.js-><TextField /> prop: InputProps should apply additional props to the Input component', 'packages/material-ui/src/TextField/TextField.test.js-... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> with an outline should set outline props'] | ['scripts/listChangedFiles.test.js->listChangedFiles should detect changes'] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TextField/TextField.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/components/text-fields/ComposedTextField.js->program->function_declaration:ComposedTextField"] |
mui/material-ui | 17,691 | mui__material-ui-17691 | ['17568'] | 9122b600f5671c7a3563f2ca73d64ef8fdf3fc1b | diff --git a/docs/pages/api/select.md b/docs/pages/api/select.md
--- a/docs/pages/api/select.md
+++ b/docs/pages/api/select.md
@@ -41,7 +41,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">open</span> | <span class="prop-type">bool</span> | | Control `sel... | diff --git a/packages/material-ui/src/InputBase/InputBase.test.js b/packages/material-ui/src/InputBase/InputBase.test.js
--- a/packages/material-ui/src/InputBase/InputBase.test.js
+++ b/packages/material-ui/src/InputBase/InputBase.test.js
@@ -594,7 +594,7 @@ describe('<InputBase />', () => {
InputProps={{
... | Value for Select which allows to not select any of the options
- [x ] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Summary 💡
In this example: https://material-ui.com/components/selects/, you see on the first select co... | @giorgi-m How would you envision this to be documented?
@oliviertassinari This is problematic only if I have InputLabel and set as value some random value, see: https://codesandbox.io/s/material-demo-w5r5f
the label is shown on top, whereas if you set value to '', then the label isn't set on top anymore.
If ... | 2019-10-03 17:14: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple selects value based on their stringified equality when theyre not objects', 'packages/material-ui/src/TablePagination/TablePaginat... | ['packages/material-ui/src/Select/Select.test.js-><Select /> prop: value warnings warns when the value is not present in any option'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/src/InputBase/InputBase.test.js test/utils/consoleError.js packages/material-ui/src/TablePagination/TablePagination.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/components/selects/DialogSelect.js->program->function_declaration:DialogSelect"] |
mui/material-ui | 17,714 | mui__material-ui-17714 | ['16631'] | 416b5f11f846515c96d2fba8e70a5beaa90e51f6 | diff --git a/docs/pages/api/slider.md b/docs/pages/api/slider.md
--- a/docs/pages/api/slider.md
+++ b/docs/pages/api/slider.md
@@ -43,6 +43,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">orientation</span> | <span class="prop-type">'horizontal'<br>|... | diff --git a/packages/material-ui/src/Slider/Slider.test.js b/packages/material-ui/src/Slider/Slider.test.js
--- a/packages/material-ui/src/Slider/Slider.test.js
+++ b/packages/material-ui/src/Slider/Slider.test.js
@@ -256,6 +256,18 @@ describe('<Slider />', () => {
});
});
+ describe('prop: track', () => {
... | [Slider] Hide the track
It doesn't seem possible to style **only** selected/current mark label for emphasis. All labels left of the thumbnails are given `markLabelActive` css. For example, users only want see rainfall chart for 2017. The way it's styled would give the impression that previous years are also included.... | > For example, users only want see rainfall chart for 2017. The way it's styled would give the impression that previous years are also included.
@vnugent Thank you for sharing the use case. It's interesting, I hadn't considered it when working on the component. Take the native browser implementations, [most](https:/... | 2019-10-05 01:14:51+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Slider/Slider.test.js-><Slider /> keyboard should reach right edge value', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> Material-UI component API should render without errors in ReactTestRenderer', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> prop: orientation sh... | ['packages/material-ui/src/Slider/Slider.test.js-><Slider /> prop: track should render the track classes for inverted', 'packages/material-ui/src/Slider/Slider.test.js-><Slider /> prop: track should render the track classes for false'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Slider/Slider.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,773 | mui__material-ui-17773 | ['11833'] | 4aea24af5b3d0749536e036dccc0eb209f18690d | diff --git a/packages/material-ui/src/Modal/Modal.js b/packages/material-ui/src/Modal/Modal.js
--- a/packages/material-ui/src/Modal/Modal.js
+++ b/packages/material-ui/src/Modal/Modal.js
@@ -207,10 +207,6 @@ const Modal = React.forwardRef(function Modal(inProps, ref) {
const inlineStyle = styles(theme || { zIndex ... | diff --git a/packages/material-ui/src/Dialog/Dialog.test.js b/packages/material-ui/src/Dialog/Dialog.test.js
--- a/packages/material-ui/src/Dialog/Dialog.test.js
+++ b/packages/material-ui/src/Dialog/Dialog.test.js
@@ -141,11 +141,10 @@ describe('<Dialog />', () => {
});
describe('backdrop', () => {
- it('ha... | [Select] Cannot interact with the component using the keyboard with NVDA opened
<!--- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
... | The same thing occurs with JAWS 2018 as well.
Have the same issue here. Without JAWS open everything works as expected, but as soon as it is running - up/down arrow keys navigation doesn't work.
I suppose it is because of the custom keyboard handlers which follow navigation programmatically and specify `tabIndex` et... | 2019-10-07 17:57:50+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> calls onEscapeKeydown when pressing Esc fo... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> focus contains the focus if the active element is removed', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> backdrop does have `role` `none presentation`', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> render should render the content int... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Dialog/Dialog.test.js packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,781 | mui__material-ui-17781 | ['17309'] | 4aea24af5b3d0749536e036dccc0eb209f18690d | diff --git a/packages/material-ui/src/Popper/Popper.js b/packages/material-ui/src/Popper/Popper.js
--- a/packages/material-ui/src/Popper/Popper.js
+++ b/packages/material-ui/src/Popper/Popper.js
@@ -78,14 +78,9 @@ const Popper = React.forwardRef(function Popper(props, ref) {
* modifiers.flip is essentially a flip f... | diff --git a/packages/material-ui/src/Popper/Popper.test.js b/packages/material-ui/src/Popper/Popper.test.js
--- a/packages/material-ui/src/Popper/Popper.test.js
+++ b/packages/material-ui/src/Popper/Popper.test.js
@@ -1,9 +1,10 @@
import React from 'react';
-import { assert } from 'chai';
+import { assert, expect } f... | [Popper] Render function `placement` argument is not updated
class MuiTooltip-tooltipPlacementBottom is always applied by default.
if props placement is set to top then MuiTooltip-tooltipPlacementTop is always applied.
It's not upated according to x-placement anymore
| null | 2019-10-08 01:35:39+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip top-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip bottom-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> Ma... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip placement when edge is reached'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popper/Popper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,829 | mui__material-ui-17829 | ['17718'] | 5d564f9c1be5bf20b51be1a479d292bf443291ba | diff --git a/docs/pages/api/chip.md b/docs/pages/api/chip.md
--- a/docs/pages/api/chip.md
+++ b/docs/pages/api/chip.md
@@ -29,7 +29,7 @@ Chips represent complex entities in small blocks, such as a contact.
| <span class="prop-name">classes</span> | <span class="prop-type">object</span> | | Override or extend the styl... | diff --git a/packages/material-ui/src/Chip/Chip.test.js b/packages/material-ui/src/Chip/Chip.test.js
--- a/packages/material-ui/src/Chip/Chip.test.js
+++ b/packages/material-ui/src/Chip/Chip.test.js
@@ -423,8 +423,8 @@ describe('<Chip />', () => {
key: ' ',
};
wrapper.find('div').simulate('... | [Chip] No Ripple effect
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] -->
- [x... | null | 2019-10-10 16:16: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip has children that generate events should call handlers for child event', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> clickable text chip should have a tabIndex prop', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to ... | ['packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip onClick is defined should call onClick when `enter` is pressed ', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip onClick is defined should call onClick when `space` is pressed '] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 17,892 | mui__material-ui-17892 | ['16409'] | a6e9efff2b1cbc977b6285a2febf15c8e2ddb933 | diff --git a/docs/pages/api/select.md b/docs/pages/api/select.md
--- a/docs/pages/api/select.md
+++ b/docs/pages/api/select.md
@@ -31,6 +31,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">IconComponent</span> | <span class="prop-type">elementType</span> |... | diff --git a/packages/material-ui/src/Select/Select.test.js b/packages/material-ui/src/Select/Select.test.js
--- a/packages/material-ui/src/Select/Select.test.js
+++ b/packages/material-ui/src/Select/Select.test.js
@@ -402,6 +402,74 @@ describe('<Select />', () => {
expect(getAllByRole('option')[1]).to.have.at... | [Select] Should have role='listbox' or 'combobox' instead of 'button'
<!--- Provide a general summary of the feature in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Ch... | > screen reader announces as 'Popup Button not pressed'
Which screen readers?
Could this problem share the same root cause with #11833?
Different screen readers announcing it little differently for example Voice over says its a 'toggle button' & chromevox extension saying as 'popup button not pressed' none of them... | 2019-10-15 18:28:29+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple selects value based on their stringified equality when theyre not objects', 'packages/material-ui/src/TextField/TextField.test.js-... | ['packages/material-ui/src/Select/Select.test.js-><Select /> accessibility is labelled by itself when it has a name', 'packages/material-ui/src/Select/Select.test.js-><Select /> accessibility can be labelled by an additional element if its id is provided in `labelId`', 'packages/material-ui/src/Select/Select.test.js-><... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/src/TextField/TextField.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 5 | 0 | 5 | false | false | ["docs/src/pages/components/selects/CustomizedSelects.js->program->function_declaration:CustomizedSelects", "docs/src/pages/components/selects/MultipleSelect.js->program->function_declaration:MultipleSelect", "docs/src/pages/components/selects/ControlledOpenSelect.js->program->function_declaration:ControlledOpenSelect"... |
mui/material-ui | 17,972 | mui__material-ui-17972 | ['17812'] | 1e4d2db346e0e31ac1b85d371ee9c375fb1545cc | diff --git a/docs/src/pages/components/modal/ServerModal.js b/docs/src/pages/components/modal/ServerModal.js
--- a/docs/src/pages/components/modal/ServerModal.js
+++ b/docs/src/pages/components/modal/ServerModal.js
@@ -4,9 +4,14 @@ import Modal from '@material-ui/core/Modal';
const useStyles = makeStyles(theme => ({... | diff --git a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
--- a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
+++ b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
@@ -77,13 +77,13 ... | Selects in Gatsby allow scrolling
<!-- Provide a general summary of the issue in the Title above -->
Using the selects component in on a Gatsby site allows you scroll. The selects box will stay with you as you scroll down the page
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
... | The problems come from *layout.css*, it's the first time I see such approach:
```css
html {
overflow-y: scroll;
}
```
Where does this template come from?
Oh boy, it's present with
```sh
npm install -g gatsby-cli
gatsby new gatsby-site
cd gatsby-site
```
Ok, maybe we should apply overflow: hidden to the... | 2019-10-21 09:00: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Snackbar/Snackbar.test.js-><Snackbar /> prop: autoHideDuration should be able to interrupt the timer', 'packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> should handle null child', 'packages/material-ui/src/Popover/Popover.test.js-><Popover /> positio... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/Popper/Popper.test.js-><Popper />... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js packages/material-ui/src/Popper/Popper.test.js packages/material-ui/src/Modal/Modal.test.js packages/material-ui/src/Snackbar/Snackbar.test.js packages/material-ui/src/Pop... | Bug Fix | false | true | false | false | 7 | 0 | 7 | false | false | ["packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:ariaHiddenSiblings", "packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:handleContainer", "packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:isHideable", "packages/material-ui/src/Moda... |
mui/material-ui | 17,978 | mui__material-ui-17978 | ['8999'] | aed1f38f17aeb25f29b9948c6134c8ed6364f1c6 | diff --git a/packages/material-ui/src/Select/SelectInput.js b/packages/material-ui/src/Select/SelectInput.js
--- a/packages/material-ui/src/Select/SelectInput.js
+++ b/packages/material-ui/src/Select/SelectInput.js
@@ -123,7 +123,11 @@ const SelectInput = React.forwardRef(function SelectInput(props, ref) {
}
};... | diff --git a/packages/material-ui/src/Select/Select.test.js b/packages/material-ui/src/Select/Select.test.js
--- a/packages/material-ui/src/Select/Select.test.js
+++ b/packages/material-ui/src/Select/Select.test.js
@@ -95,13 +95,13 @@ describe('<Select />', () => {
const { getByRole, getAllByRole, queryByRole } = ... | [Select] Feels less response than native counterpart
- [x] I have searched the [issues](https://github.com/callemall/material-ui/issues) of this repository and believe that this is not a duplicate.
## Expected Behavior
When I use a Select Field, it should "feel" responsive and fast. Currently, before the menu with ... | One important thing to take into account: the behavior should stay the same for touch interactions as we need to filter our scroll touch interactions.
I hope it's as simple as implemented as replacing the onClick by onMouseDown event callback.
https://github.com/callemall/material-ui/blob/7064086473f255bd48fcfc2987b03... | 2019-10-21 13:55:10+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/test/integration/Select.test.js-><Select> integration with label is displayed as focused while open', 'packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple select... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should ignore onBlur when the menu opens', 'packages/material-ui/test/integration/Select.test.js-><Select> integration with Dialog should focus the selected item', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple prop: onChange shoul... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/test/integration/Select.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,026 | mui__material-ui-18026 | ['17876'] | e09870b89fff559a97272713a8c2513262950c6f | diff --git a/docs/pages/api/avatar.md b/docs/pages/api/avatar.md
--- a/docs/pages/api/avatar.md
+++ b/docs/pages/api/avatar.md
@@ -25,7 +25,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| Name | Type | Default | Description |
|:-----|:-----|:--------|:------------|
| <span cla... | diff --git a/packages/material-ui/src/Avatar/Avatar.test.js b/packages/material-ui/src/Avatar/Avatar.test.js
--- a/packages/material-ui/src/Avatar/Avatar.test.js
+++ b/packages/material-ui/src/Avatar/Avatar.test.js
@@ -58,6 +58,20 @@ describe('<Avatar />', () => {
});
});
+ describe('image avatar with unrend... | Avatar shows children and image
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
When I pass in children and a `src` prop to the `Avatar` componen... | @ajdaniel It sounds like you have to pick between one of the two approaches. Why do you mix both?
That's how it worked before. The children prop became a fallback and I didn't have to code the logic of showing or hiding the children based on the image availability, it just did that automatically.
The children prop desc... | 2019-10-24 23:16: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Avatar/Avatar.test.js-><Avatar /> Material-UI component API ref attaches the ref', 'packages/material-ui/src/Avatar/Avatar.test.js-><Avatar /> svg icon avatar should merge user classes & spread custom props to the root node', 'packages/material-ui/src/Avatar/Avatar.test.js-><Avatar /> falsey ... | ['packages/material-ui/src/Avatar/Avatar.test.js-><Avatar /> image avatar with unrendered children should render a div containing an img, not children'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Avatar/Avatar.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,032 | mui__material-ui-18032 | ['17999'] | cec2f0caf91f5ea235e1a62a8c6c2493075927ef | diff --git a/docs/pages/api/dialog.md b/docs/pages/api/dialog.md
--- a/docs/pages/api/dialog.md
+++ b/docs/pages/api/dialog.md
@@ -24,6 +24,8 @@ Dialogs are overlaid modal paper based components with a backdrop.
| Name | Type | Default | Description |
|:-----|:-----|:--------|:------------|
+| <span class="prop-nam... | diff --git a/packages/material-ui/src/Dialog/Dialog.test.js b/packages/material-ui/src/Dialog/Dialog.test.js
--- a/packages/material-ui/src/Dialog/Dialog.test.js
+++ b/packages/material-ui/src/Dialog/Dialog.test.js
@@ -264,4 +264,20 @@ describe('<Dialog />', () => {
expect(getByTestId('paper')).to.have.class('cu... | [Dialogs, accessibility] NVDA doesn't read anything after open a dialog
1. After open any dialog, NVDA doesn't read anything, it works after press tab and move focus to actionable element (note: if any actionable element exists on dialog)
2. It works when we put some element with autoFocus. but with JAWS on IE it is n... | null | 2019-10-25 09:03:56+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> prop: fullWidth should set `fullWidth` class if specified', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui/src/Dialog/Dialog.test.j... | ['packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> a11y can be labelled by another element'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Dialog/Dialog.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 8 | 0 | 8 | false | false | ["docs/src/pages/components/dialogs/ConfirmationDialog.js->program->function_declaration:ConfirmationDialogRaw", "docs/src/pages/components/dialogs/MaxWidthDialog.js->program->function_declaration:MaxWidthDialog", "docs/src/pages/components/dialogs/ResponsiveDialog.js->program->function_declaration:ResponsiveDialog", "... |
mui/material-ui | 18,117 | mui__material-ui-18117 | ['18110'] | c28697d0ba4c891f826133a77e58f298dc50c4bb | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -163,14 +163,19 @@ export default ... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -1,16 +1,17 @@
import React from 'rea... | [AutoComplete] Multiple + freeSolo crash
I was playing around with the Autocomplete component in codesandbox to see if it would be worth switching to from react-select. Unfortunately, I can very reliably trigger a page crash due to an error occurring in the <ForwardRef(Autocomplete)> component.
<!-- Checked checkbo... | @ideoclickVanessa Thanks for the report! I assure you, it's not the only way to crash the component. In a week or two, it will be more reliable 💪. You can follow our progress with https://github.com/mui-org/material-ui/labels/component%3A%20Autocomplete.
What do you think of this diff?
```diff
diff --git a/packages/... | 2019-10-31 08:12:37+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API should render without errors in Reac... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> multiple should not crash'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,131 | mui__material-ui-18131 | ['18130'] | 66106867454e17f308463be056088dd7cc5946bb | diff --git a/packages/material-ui/src/InputBase/InputBase.js b/packages/material-ui/src/InputBase/InputBase.js
--- a/packages/material-ui/src/InputBase/InputBase.js
+++ b/packages/material-ui/src/InputBase/InputBase.js
@@ -328,7 +328,7 @@ const InputBase = React.forwardRef(function InputBase(props, ref) {
}
... | diff --git a/packages/material-ui/src/InputBase/InputBase.test.js b/packages/material-ui/src/InputBase/InputBase.test.js
--- a/packages/material-ui/src/InputBase/InputBase.test.js
+++ b/packages/material-ui/src/InputBase/InputBase.test.js
@@ -558,6 +558,43 @@ describe('<InputBase />', () => {
});
});
+ descr... | onChange behavior has changed between core@v4.5.1 and core@4.5.2
As discussed with @oliviertassinari the InputBase elements onChange behavior has changed.
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believ... | null | 2019-11-01 07:15:22+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> with FormControl propagates filled state when uncontrolled', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> with FormControl registering input should not warn when toggling between inputs', 'packages/material-ui/src/InputBase/In... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent with prop: inputProps should call onChange inputProp callback with all params sent from custom inputComponent'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputBase/InputBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,141 | mui__material-ui-18141 | ['18097'] | 13b3a0d31947ccdb20108febb5432d4f46f5a677 | diff --git a/docs/src/pages/components/text-fields/ValidationTextFields.js b/docs/src/pages/components/text-fields/ValidationTextFields.js
--- a/docs/src/pages/components/text-fields/ValidationTextFields.js
+++ b/docs/src/pages/components/text-fields/ValidationTextFields.js
@@ -30,7 +30,7 @@ export default function Val... | diff --git a/packages/material-ui/src/TextField/TextField.test.js b/packages/material-ui/src/TextField/TextField.test.js
--- a/packages/material-ui/src/TextField/TextField.test.js
+++ b/packages/material-ui/src/TextField/TextField.test.js
@@ -117,10 +117,10 @@ describe('<TextField />', () => {
});
describe('pro... | TextField with select=true and native does not add the DOM ID to the select element
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
Using `TextFi... | Follow up: Adding the `id` to `inputProps` seems to restore the previous behavior. Is that the preferred way to handle it?
> Follow up: Adding the `id` to `inputProps` seems to restore the previous behavior. Is that the preferred way to handle it?
I think we fix `InputLabel` having a `for` value since the labeling ... | 2019-11-01 16:07:26+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> structure should forward the fullWidth prop to Input', 'packages/material-ui/src/TextField/TextField.test.js-><TextField /> prop: InputProps should apply additional props to the Input component', 'packages/material-ui/src/TextField/TextField.test.js-... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> prop: select associates the label with the <select /> when `native={true}` and `id`'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TextField/TextField.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/components/text-fields/ValidationTextFields.js->program->function_declaration:ValidationTextFields"] |
mui/material-ui | 18,153 | mui__material-ui-18153 | ['18081'] | 262c8cfc4c47cad7e1bfc34f50e36ec78e9e976a | diff --git a/docs/pages/api/autocomplete.md b/docs/pages/api/autocomplete.md
--- a/docs/pages/api/autocomplete.md
+++ b/docs/pages/api/autocomplete.md
@@ -60,7 +60,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">renderGroup</span> | <span class="prop-type... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -51,6 +51,23 @@ describe('<Autocomplet... | [Docs] Autocomplete Multiple Values delete bug
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
Clicking the delete button for an option in the "M... | On the same page, but unrelated to the issue, the following is written:
> The component exposes a factory to create a filter method that can provided to the `filerOption` prop. You can use it to change the default option filter behavior.
I guess that's supposed to say `filterOption` and not `filerOption`.
@Studio... | 2019-11-02 17:33:26+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> multiple should remove the last option'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete", "docs/src/pages/components/autocomplete/Tags.js->program->function_declaration:Tags", "docs/src/pages/components/autocomplete/CustomizedHook.js->program->function_declaration:CustomizedHook", "docs/src/pag... |
mui/material-ui | 18,154 | mui__material-ui-18154 | ['17700'] | 8a78af8f1097102ee4f09625e6eb7fdb683560f5 | diff --git a/packages/material-ui-lab/src/TreeItem/TreeItem.js b/packages/material-ui-lab/src/TreeItem/TreeItem.js
--- a/packages/material-ui-lab/src/TreeItem/TreeItem.js
+++ b/packages/material-ui-lab/src/TreeItem/TreeItem.js
@@ -81,7 +81,8 @@ const TreeItem = React.forwardRef(function TreeItem(props, ref) {
focu... | diff --git a/packages/material-ui-lab/src/TreeView/TreeView.test.js b/packages/material-ui-lab/src/TreeView/TreeView.test.js
--- a/packages/material-ui-lab/src/TreeView/TreeView.test.js
+++ b/packages/material-ui-lab/src/TreeView/TreeView.test.js
@@ -21,6 +21,38 @@ describe('<TreeView />', () => {
after: () => mou... | [TreeView] Locks up preventing mouse & up/down arrows from working
<!-- Provide a general summary of the issue in the Title above -->
TreeView will often lock up, preventing mouse up/down arrows from working. This happens after it has re-rendered, even if the tree data hasn't changed.
<!--
Thank you very much ... | Exact key press sequence to cause error
1. click first item
2. down, right, up, down
3. down will not respond anymore
4. press left arrow to make it work again
Thanks for the report, @eps1lon was experiencing something similar. I can pick this up and look into it at the same time. It wouldn’t surprise me if they ar... | 2019-11-02 19:31:22+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> Accessibility (TreeView) should have the role `tree`', 'packages/material-ui-lab/src/T... | ['packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> should not error when component state changes'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/TreeView/TreeView.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/TreeView/TreeView.js->program->function_declaration:arrayDiff"] |
mui/material-ui | 18,161 | mui__material-ui-18161 | ['18123'] | b06c284d830d39fb41f79fb40d3904fd1f67a12f | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -171,8 +171,26 @@ export default f... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -2,6 +2,7 @@ import React from 'react'... | Autocomplete with freeSolo and custom onChange breaks on Enter key pressed
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Chec... | @oziniak Thank you for the report! What do you think of this fix?
```diff
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index 7f28ddca2..d7394c18b 100644
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplet... | 2019-11-03 15:03:38+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> warnings warn if getOptionLabel do not return a string'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,165 | mui__material-ui-18165 | ['17705'] | 522ea5ac24de075c07aaaa69723a88c0f97bdac4 | diff --git a/docs/pages/api/tree-view.md b/docs/pages/api/tree-view.md
--- a/docs/pages/api/tree-view.md
+++ b/docs/pages/api/tree-view.md
@@ -28,10 +28,11 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">classes</span> | <span class="prop-type">object</span... | diff --git a/packages/material-ui-lab/src/TreeView/TreeView.test.js b/packages/material-ui-lab/src/TreeView/TreeView.test.js
--- a/packages/material-ui-lab/src/TreeView/TreeView.test.js
+++ b/packages/material-ui-lab/src/TreeView/TreeView.test.js
@@ -4,6 +4,7 @@ import { spy } from 'sinon';
import { createClientRender... | TreeView - Expand TreeItem manually
I'm wondering if there is a way to open TreeItem manually? If I have a node "Add item" with a child node "Items", is there a way to expand "Items" once a new item is added?
What is the recommended way of achieving what I want?
Here is a [Codesandbox](https://codesandbox.io/s/wi... | @pimeh @flurmbo What do you think of allowing the *expanded* state to be controlled?
Right now, we have a `defaultExpanded` prop that supports the uncontrollable approach but nothing for the controlled way. A new `expanded`, and `onExpanded` props could solve this problem.
@oliviertassinari I think that's much better... | 2019-11-04 00:01:20+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> Accessibility (TreeView) should have the role `tree`', 'packages/material-ui-lab/src/T... | ['packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> warnings should warn when switching from controlled to uncontrolled', 'packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> should be able to be controlled', 'packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> onNod... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/TreeView/TreeView.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,229 | mui__material-ui-18229 | ['18221'] | 7f09ea46f380eed609ca9d348022f77a67e787bb | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -527,7 +527,7 @@ export default fu... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -421,7 +421,7 @@ describe('<Autocomple... | Autocomplete crash in multiple selection mode
<!-- Provide a general summary of the issue in the Title above -->
When multiple selections are enabled on an Autocomplete component, it's possible to crash the component by
1. Clearing all options
2. Selecting a valid option
3. Pressing `Enter`
This can be duplicat... | @stevemoncada Thank you for the report, It's the same root cause as #18211. The proposed fix applies here too. | 2019-11-06 11:16:17+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> enter select a single value when enter is pressed', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> enter select multiple value when enter is pressed'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,247 | mui__material-ui-18247 | ['18245'] | 4d260e8ce7cd4889146ffb22535881cc3718d80e | diff --git a/packages/material-ui/src/styles/createPalette.js b/packages/material-ui/src/styles/createPalette.js
--- a/packages/material-ui/src/styles/createPalette.js
+++ b/packages/material-ui/src/styles/createPalette.js
@@ -1,10 +1,10 @@
import { deepmerge } from '@material-ui/utils';
+import common from '../colors... | diff --git a/packages/material-ui/src/styles/createPalette.test.js b/packages/material-ui/src/styles/createPalette.test.js
--- a/packages/material-ui/src/styles/createPalette.test.js
+++ b/packages/material-ui/src/styles/createPalette.test.js
@@ -1,7 +1,7 @@
import { assert } from 'chai';
import consoleErrorMock from... | createMuiTheme modifies previously created theme
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
When creating multiple themes in succession, pr... | I assume this is due to: https://github.com/mui-org/material-ui/blob/4d260e8ce7cd4889146ffb22535881cc3718d80e/packages/material-ui/src/styles/createPalette.js#L200
Since clone is set to false, the theme defaults will be modified as the passed in target by the new custom deepmerge implementation, and also the created... | 2019-11-07 06:20: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/styles/createPalette.test.js->createPalette() should create a material design palette according to spec', 'packages/material-ui/src/styles/createPalette.test.js->createPalette() augmentColor should throw when the input is invalid', 'packages/material-ui/src/styles/createPalette.test.js->creat... | ['packages/material-ui/src/styles/createPalette.test.js->createPalette() should create a palette with unique object references'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/styles/createPalette.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/styles/createPalette.js->program->function_declaration:createPalette"] |
mui/material-ui | 18,257 | mui__material-ui-18257 | ['18255'] | b29c294f55f0dca2af0c8438b86961a8c8534516 | diff --git a/packages/material-ui/src/Select/Select.js b/packages/material-ui/src/Select/Select.js
--- a/packages/material-ui/src/Select/Select.js
+++ b/packages/material-ui/src/Select/Select.js
@@ -69,7 +69,7 @@ const Select = React.forwardRef(function Select(props, ref) {
type: undefined, // We render a select... | diff --git a/packages/material-ui/src/Select/Select.test.js b/packages/material-ui/src/Select/Select.test.js
--- a/packages/material-ui/src/Select/Select.test.js
+++ b/packages/material-ui/src/Select/Select.test.js
@@ -867,4 +867,23 @@ describe('<Select />', () => {
expect(getByRole('button')).to.have.attribute(... | Regression: <Select native id="my-id"> No Longer Has an Id
The "id" prop is ignored for \<Select\>'s that have the "native" prop set.
At some point in the past (maybe a few versions ago) this use to work.
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-... | null | 2019-11-07 14:39:54+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: multiple selects value based on their stringified equality when theyre not objects', 'packages/material-ui/src/Select/Select.test.js-><Sele... | ['packages/material-ui/src/Select/Select.test.js-><Select /> prop: native can be labelled with a <label />'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/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 | 18,281 | mui__material-ui-18281 | ['18133'] | 3d393bfc56c2de4ebb080de0a5541b4a9b905122 | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -88,13 +88,6 @@ export default fun... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -110,7 +110,7 @@ describe('<Autocomple... | [Autocomplete] Some WAI-ARIA attributes are incorrect
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should l... | > aria-controls should only exist when the listbox is present in the DOM. Remove the attribute from the input whenever the listbox itself is removed.
Is this actually an issue with assistive technology or is this just warning for authors that this has no effect? Since the markup is rendered by another library (Mater... | 2019-11-09 12:58:53+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> WAI-ARIA conforming markup should add and remove aria-activedescendant'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,285 | mui__material-ui-18285 | ['18113'] | 0e0f17e61e43e6f0af0e5636479133baf54db6e9 | diff --git a/docs/pages/api/autocomplete.md b/docs/pages/api/autocomplete.md
--- a/docs/pages/api/autocomplete.md
+++ b/docs/pages/api/autocomplete.md
@@ -46,6 +46,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">groupBy</span> | <span class="prop-type">fu... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -549,4 +549,34 @@ describe('<Autocompl... | [Autocomplete] freeSolo is not actually usable
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
If you use an Autocomplete with `freeSolo` the `on... | > In freeSolo mode onChange should fire on every input key press like a normal TextField does.
The onChange and value props for the freeSolo are meant to account for user confirmation (click / enter). The google place demo access the input value like this:
https://github.com/mui-org/material-ui/blob/c28697d0ba4c89... | 2019-11-09 18:48: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> controlled input controls the input value'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete", "packages/material-ui/src/utils/useEventCallback.js->program->function_declaration:useEventCallback"] |
mui/material-ui | 18,286 | mui__material-ui-18286 | ['18203'] | ba1f645a2dbed510ca40a53de1707dda78adae53 | diff --git a/docs/src/pages/components/autocomplete/CustomizedHook.js b/docs/src/pages/components/autocomplete/CustomizedHook.js
--- a/docs/src/pages/components/autocomplete/CustomizedHook.js
+++ b/docs/src/pages/components/autocomplete/CustomizedHook.js
@@ -124,7 +124,7 @@ const Listbox = styled('ul')`
export defau... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -497,4 +497,56 @@ describe('<Autocompl... | [Autocomplete] Multi-select pop-up not shown when already focused
## Current Behavior 😯
When clicking on the input rendered by the Autocomplete, it pops up with the available selections. The user selects a value, after which the input shows the selected option as a chip. When the user then clicks inside of the inpu... | @FlorisWarmenhoven Thank you for the report. What do you think of implementing this toggle behavior when the input is empty, and only?
I have tried something like this to get a sense of the UX it produces
```diff
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-la... | 2019-11-09 22:56: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> click input toggles if empty', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: autoComplete add a completion string', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete ... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["docs/src/pages/components/autocomplete/UseAutocomplete.js->program->function_declaration:UseAutocomplete", "packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete", "docs/src/pages/components/autocomplete/CustomizedHook.js->program->function_declaration:Customiz... |
mui/material-ui | 18,306 | mui__material-ui-18306 | ['17375'] | 0e0f17e61e43e6f0af0e5636479133baf54db6e9 | diff --git a/packages/material-ui-codemod/src/v4.0.0/top-level-imports.js b/packages/material-ui-codemod/src/v4.0.0/top-level-imports.js
--- a/packages/material-ui-codemod/src/v4.0.0/top-level-imports.js
+++ b/packages/material-ui-codemod/src/v4.0.0/top-level-imports.js
@@ -1,23 +1,19 @@
-import { dirname } from 'path'... | diff --git a/packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js b/packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js
--- a/packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js
+++ b/packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js
@@ -17,7 +17,10 @@ describe('... | typescript definitions not available on root of @material-ui/core
Why can I do:
```ts
import { IconButton } from '@material-ui/core'
```
but not:
```ts
import { IconButtonProps } from '@material-ui/core'
```
instead I have to do
```ts
import { IconButtonProps } from '@material-ui/core/IconButton'
`... | null | 2019-11-10 16:17:20+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js->@material-ui/codemod v4.0.0 top-level-imports should be idempotent'] | ['packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js->@material-ui/codemod v4.0.0 top-level-imports convert path as needed'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-codemod/src/v4.0.0/top-level-imports.test/actual.js packages/material-ui-codemod/src/v4.0.0/top-level-imports.test.js packages/material-ui-codemod/src/v4.0.0/top-level-imports.test/expected.js --reporter /testbed/custom... | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-codemod/src/v4.0.0/top-level-imports.js->program->function_declaration:transformer"] |
mui/material-ui | 18,357 | mui__material-ui-18357 | ['16795'] | deb31c7a1a933f9d9d3abdceab4d9e78b7bc027b | diff --git a/docs/pages/api/tree-item.md b/docs/pages/api/tree-item.md
--- a/docs/pages/api/tree-item.md
+++ b/docs/pages/api/tree-item.md
@@ -48,6 +48,7 @@ Any other props supplied will be provided to the root element (native element).
|:-----|:-------------|:------------|
| <span class="prop-name">root</span> | <sp... | diff --git a/packages/material-ui-lab/src/TreeItem/TreeItem.test.js b/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
--- a/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
+++ b/packages/material-ui-lab/src/TreeItem/TreeItem.test.js
@@ -151,13 +151,13 @@ describe('<TreeItem />', () => {
describe('Acc... | [Treeview] Node selection support
Thanks very much for the release of the brand new TreeView component! ❤️
I'd like to request a basic feature for the Treeview component to emit an event when any node is selected.
You may have already planned this, but I couldn't find any information for it, hence the request.
<... | null | 2019-11-13 22:30:50+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN jq 'del(.devDependencies["vrtest-mui"])' package.json > package.json.tmp && mv package.json.tmp package.json
RUN . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && rm -rf node_modules && yarn install && yarn add -D -W @types/prop-types @types/react-dom @types/s... | ['packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> Accessibility Expansion enter key interaction expands a node with children', 'packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> Material-UI component API applies the root class to the root component if it has this class', 'package... | ['packages/material-ui-lab/src/TreeView/TreeView.test.js-><TreeView /> should be able to be controlled with the selected prop and multiSelect', 'packages/material-ui-lab/src/TreeItem/TreeItem.test.js-><TreeItem /> Accessibility Multi Selection range selection keyboard arrow', 'packages/material-ui-lab/src/TreeItem/Tree... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/TreeView/TreeView.test.js packages/material-ui-lab/src/TreeItem/TreeItem.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 6 | 0 | 6 | false | false | ["docs/src/pages/components/tree-view/ControlledTreeView.js->program->function_declaration:ControlledTreeView", "docs/src/pages/components/tree-view/CustomizedTreeView.js->program->function_declaration:PlusSquare", "docs/src/pages/components/tree-view/FileSystemNavigator.js->program->function_declaration:FileSystemNavi... |
mui/material-ui | 18,361 | mui__material-ui-18361 | ['18353'] | 9e23e46eac58b0fc32f5f2859e85e77b014a2618 | diff --git a/packages/material-ui/src/Snackbar/Snackbar.js b/packages/material-ui/src/Snackbar/Snackbar.js
--- a/packages/material-ui/src/Snackbar/Snackbar.js
+++ b/packages/material-ui/src/Snackbar/Snackbar.js
@@ -4,6 +4,7 @@ import clsx from 'clsx';
import withStyles from '../styles/withStyles';
import { duration }... | diff --git a/packages/material-ui/src/Snackbar/Snackbar.test.js b/packages/material-ui/src/Snackbar/Snackbar.test.js
--- a/packages/material-ui/src/Snackbar/Snackbar.test.js
+++ b/packages/material-ui/src/Snackbar/Snackbar.test.js
@@ -1,7 +1,8 @@
import React from 'react';
-import { assert } from 'chai';
+import { exp... | [Snackbar] Auto hide timer restarts when parent component re-renders
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked ch... | @ambersz Thank you for the report. Right, it comes from the new reference of `onClose` you provide at each render, it resets the logic. We should be able to work around it, and simplify the logic with:
```diff
diff --git a/packages/material-ui/src/Snackbar/Snackbar.js b/packages/material-ui/src/Snackbar/Snackbar.js... | 2019-11-14 02:44:27+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Snackbar/Snackbar.test.js-><Snackbar /> prop: disableWindowBlurListener should not pause auto hide when disabled and window lost focus', 'packages/material-ui/src/Snackbar/Snackbar.test.js-><Snackbar /> prop: autoHideDuration should be able to interrupt the timer', 'packages/material-ui/src/S... | ['packages/material-ui/src/Snackbar/Snackbar.test.js-><Snackbar /> prop: autoHideDuration calls onClose at timeout even if the prop changes'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Snackbar/Snackbar.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,380 | mui__material-ui-18380 | ['18360'] | 64ae0c6a2024e9e658a998029f33be8a2cdedce4 | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -672,15 +672,16 @@ export default ... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -294,6 +294,40 @@ describe('<Autocompl... | Autocomplete disableOpenOnFocus not working
Summary: Autocomplete disableOpenOnFocus not working
"4.0.0-alpha.32"
[X] The issue is present in the latest release.
[X] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Curren... | @jcmoore0 Thank you for reporting this regression. It's a good signal for us that it's time to add a regression test for it. What do you think of this diff?
```diff
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index d... | 2019-11-15 08:58:40+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: disableOpenOnFocus disables open on input focus'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,381 | mui__material-ui-18381 | ['18373'] | 64ae0c6a2024e9e658a998029f33be8a2cdedce4 | diff --git a/packages/material-ui/src/Popper/Popper.js b/packages/material-ui/src/Popper/Popper.js
--- a/packages/material-ui/src/Popper/Popper.js
+++ b/packages/material-ui/src/Popper/Popper.js
@@ -2,20 +2,17 @@ import React from 'react';
import PropTypes from 'prop-types';
import PopperJS from 'popper.js';
import ... | diff --git a/packages/material-ui/src/Popper/Popper.test.js b/packages/material-ui/src/Popper/Popper.test.js
--- a/packages/material-ui/src/Popper/Popper.test.js
+++ b/packages/material-ui/src/Popper/Popper.test.js
@@ -3,6 +3,7 @@ import { assert, expect } from 'chai';
import { spy, useFakeTimers } from 'sinon';
impo... | Popper.js document is not defined with SSR
I need help with SSR using the `Popper` component.
When I access to my page via a link from another page, the page is rendered as it should be.
But when I try to access the same page directly from its url, I get an HTTP error 500 and this error message:
```
Error ru... | This concern is related to https://github.com/mui-org/material-ui/issues/15798#issuecomment-495078241. In this context, I would suggest this diff:
```diff
diff --git a/packages/material-ui/src/Popper/Popper.js b/packages/material-ui/src/Popper/Popper.js
index 80f5f9909..da7f77e6c 100644
--- a/packages/material-ui/s... | 2019-11-15 09:02:20+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> Material-UI component API does spread props to the root component', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: keepMounted by default should remove the transition children in the DOM when closed whilst transition status is entering', 'p... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip bottom-start when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: placement should flip bottom-end when direction=rtl is used', 'packages/material-ui/src/Popper/Popper.test.js-><Popper /> p... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popper/Popper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Popper/Popper.js->program->function_declaration:flipPlacement"] |
mui/material-ui | 18,445 | mui__material-ui-18445 | ['18336'] | 9c2f734d053ea48f5ad10769687a3b0971dfa4fe | diff --git a/packages/material-ui/src/Modal/ModalManager.js b/packages/material-ui/src/Modal/ModalManager.js
--- a/packages/material-ui/src/Modal/ModalManager.js
+++ b/packages/material-ui/src/Modal/ModalManager.js
@@ -64,7 +64,10 @@ function handleContainer(containerInfo, props) {
// Improve Gatsby support
/... | diff --git a/packages/material-ui/src/Modal/Modal.test.js b/packages/material-ui/src/Modal/Modal.test.js
--- a/packages/material-ui/src/Modal/Modal.test.js
+++ b/packages/material-ui/src/Modal/Modal.test.js
@@ -632,11 +632,11 @@ describe('<Modal />', () => {
};
const wrapper = mount(<TestCase open={fals... | [Modal] html overflow hidden issue
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should look like this: [x] ... | #17972 related?
There are a lot of changes in that PR. My guess would be possibly the changes to ModalManager.js. Based on what I'm experiencing L67 looks like maybe the culprit.
Well, it would potentially explain the scrollbar still showing. Not seeing anything there that would change the scroll position.
Also... | 2019-11-19 00:54:59+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should attach a handler to the backd... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> two modal at the same time should open and close', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> two modal at the same time should open and close with Transitions', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: closeAfterTransition wh... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:handleContainer"] |
mui/material-ui | 18,480 | mui__material-ui-18480 | ['18462'] | 58f0d04c103b0e2500a6a927087b006b2537f663 | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -11,12 +11,30 @@ function stripDia... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -658,4 +658,38 @@ describe('<Autocompl... | [Autocomplete] Search includes object key values as match
## Current Behavior 😯
Developer supplies an array of objects, that has the shape of:
```
[
{
code: 'AD',
label: 'Andorra',
phone: '376',
},
// etc
]
```
When the user types 'code' or 'label' or 'phone', all values are still prese... | @FlorisWarmenhoven Thanks for the bug report. The best option is to provide your own filter and stringify method. https://material-ui.com/components/autocomplete/#custom-filter
However, I do think that we can improve the current tradeoff. I would imagine something like this:
```diff
diff --git a/packages/materia... | 2019-11-21 11:18:10+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: filterOptions should ignore object keys by default'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:defaultStringify", "packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:createFilterOptions"] |
mui/material-ui | 18,571 | mui__material-ui-18571 | ['18568'] | 38ffc1097c1be86a24920841a8a3c8979fe2e70c | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -210,6 +210,10 @@ export default f... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -650,11 +650,10 @@ describe('<Autocomp... | [Autocomplete] onInputChange it's fired in wrong moments
I don't know if I'm not understanding how it works or it's a bug, but onInputChange is executed when the component is mounted and when the TextField loses the focus.
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://... | @sclavijo93 How does it cause an issue in your end?
I guess we could only trigger the event if the value actually changes. Would it solve your problem?
```diff
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index f833a0... | 2019-11-26 02:33:46+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> controlled input controls the input value'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,611 | mui__material-ui-18611 | ['18590', '18456'] | a5f4a4dd7457bc99373e46e3732a278e3e783294 | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -371,7 +371,7 @@ export default fu... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -34,7 +34,7 @@ describe('<Autocomplete... | [Autocomplete] onChange undefined intermittently when options updated
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked c... | Similar behaviour occurs when using the "multiple", "filterSelectedOptions", "disableCloseOnSelect" props together, and selecting multiple options without moving the mouse after selection.
codesandbox: [https://codesandbox.io/s/material-demo-f5sfu](https://codesandbox.io/s/material-demo-f5sfu)
@jellyedwards @Dror88 ... | 2019-11-28 15:11:59+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: options should keep focus on selected option and not reset to top option when options updated', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: options should not select undefined '] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,683 | mui__material-ui-18683 | ['18670'] | dfe2779b8b6499ccd1922990ac9178d84e02f8b6 | diff --git a/packages/material-ui/src/useMediaQuery/useMediaQuery.js b/packages/material-ui/src/useMediaQuery/useMediaQuery.js
--- a/packages/material-ui/src/useMediaQuery/useMediaQuery.js
+++ b/packages/material-ui/src/useMediaQuery/useMediaQuery.js
@@ -1,9 +1,6 @@
import React from 'react';
import { getThemeProps, ... | diff --git a/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js b/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js
--- a/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js
+++ b/packages/material-ui/src/useMediaQuery/useMediaQuery.test.js
@@ -7,7 +7,7 @@ import { createRender } from '@ma... | [useMediaQuery] hydrationCompleted is true before hydrated
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
The `hydrationCompleted` variable in `... | These singleton variables are always problematic since they assume a whole lot about app and react implementation details.
I don't think these variables are ever correct. What we should do is identify if we actually can use the browser API during render or not. And I think the answer is No for all media queries.
... | 2019-12-04 15:56:17+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery with feature option: defaultMatches should be false by default', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth isWidthUp should work as exclusive', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth theme prop... | ['packages/material-ui/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery with feature option: defaultMatches should take the option into account', 'packages/material-ui/src/useMediaQuery/useMediaQuery.test.js->useMediaQuery with feature option: noSsr should render twice if the default value does not match the expe... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/withWidth/withWidth.test.js packages/material-ui/src/useMediaQuery/useMediaQuery.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/useMediaQuery/useMediaQuery.js->program->function_declaration:useMediaQuery", "packages/material-ui/src/useMediaQuery/useMediaQuery.js->program->function_declaration:testReset"] |
mui/material-ui | 18,687 | mui__material-ui-18687 | ['18679'] | 1073d824868d7878283a466f374bacf218f0bd42 | diff --git a/packages/material-ui/src/Tooltip/Tooltip.js b/packages/material-ui/src/Tooltip/Tooltip.js
--- a/packages/material-ui/src/Tooltip/Tooltip.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.js
@@ -280,7 +280,11 @@ const Tooltip = React.forwardRef(function Tooltip(props, ref) {
const handleEnter = event => ... | diff --git a/packages/material-ui/src/Tooltip/Tooltip.test.js b/packages/material-ui/src/Tooltip/Tooltip.test.js
--- a/packages/material-ui/src/Tooltip/Tooltip.test.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.test.js
@@ -1,5 +1,6 @@
+/* eslint-disable jsx-a11y/mouse-events-have-key-events */
import React from 'r... | [Slider] Interactive tooltips on range slider has inconsistent behavior
When you add custom Tooltip components to a slider, and you use a range, with the tooltips set to `interactive: true, leaveDelay: 100`, when you take your cursor off the second handle, it briefly shows the first handle's tooltip.
Here's a simple... | @Floriferous Why do you set `interactive` in the first place?
Well because I want my users to be able to interact with the tooltip, and copy paste the text for example, if I decide to display more information inside the tooltip based on the slider's value for example.
I had a look at the problem. In the slider, `event... | 2019-12-04 18:40:25+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: delay should take the enterDelay into account', 'packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: overrides should be transparent for the onMouseOver event', 'packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: over... | ['packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> prop: overrides should ignore event from the tooltip'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/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 | 18,744 | mui__material-ui-18744 | ['16357'] | 53ef743ec2d8f08286f2e0d56ceaea0765417e39 | diff --git a/docs/pages/api/button.md b/docs/pages/api/button.md
--- a/docs/pages/api/button.md
+++ b/docs/pages/api/button.md
@@ -29,6 +29,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">color</span> | <span class="prop-type">'default'<br>| 'in... | diff --git a/packages/material-ui/src/Button/Button.test.js b/packages/material-ui/src/Button/Button.test.js
--- a/packages/material-ui/src/Button/Button.test.js
+++ b/packages/material-ui/src/Button/Button.test.js
@@ -309,6 +309,13 @@ describe('<Button />', () => {
expect(button.querySelector('.touch-ripple')).to... | [Buttons] Disable elevation
I have buttons that I don't want to have a box-shadow. Instead of custom CSS, using the `elevation` key would be ideal for me, as that's how we handle `<Paper />` shadows
| I’m not sure if this should be in the core library. I guess we should see what other users wants. I would close this in the mean time let’s see what @oliviertassinari thinks :)
@joshwooding I agree. Personally, I would override the box shadow, or start from the ButtonBase component.
It just seems kind of 'silly' for p... | 2019-12-08 14:57: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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/Button/Button.test.js-><Button /> Material-UI component API applies the className to the root component', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render an inherit outlined button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a large ou... | ['packages/material-ui/src/Button/Button.test.js-><Button /> can disable the elevation'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Button/Button.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,754 | mui__material-ui-18754 | ['18691'] | 36f0ce344400adaf1850f2e1e8537dac463681f2 | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.js b/packages/material-ui/src/ButtonBase/ButtonBase.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.js
@@ -219,7 +219,15 @@ const ButtonBase = React.forwardRef(function ButtonBase(props, ref) {
... | diff --git a/packages/material-ui/src/ButtonBase/ButtonBase.test.js b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
--- a/packages/material-ui/src/ButtonBase/ButtonBase.test.js
+++ b/packages/material-ui/src/ButtonBase/ButtonBase.test.js
@@ -715,6 +715,32 @@ describe('<ButtonBase />', () => {
expect(o... | [Select] Opening a focused Select field using the space key does not work as expected
- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
## Current Behavior 😯
When intera... | @matt-downs The behavior changed in #18319, @eps1lon Is on it :) | 2019-12-09 11:49:45+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> ripple interactions should restart the ripple when the mouse is pressed again', 'packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed ArrowUp key on select', 'packages/material-ui/src/Select/Select.test.js-><Sel... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should open menu when pressed key on select', 'packages/material-ui/src/Select/Select.test.js-><Select /> prevents the default when releasing Space on the children', 'packages/material-ui/src/ButtonBase/ButtonBase.test.js-><ButtonBase /> event: keydown keyb... | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/Select.test.js packages/material-ui/src/ButtonBase/ButtonBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,768 | mui__material-ui-18768 | ['18764'] | 333749d2b7dfcb7b0990fe56e17d92f41aeda369 | diff --git a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js
--- a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js
+++ b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.js
@@ -40,10 +40,12 @@ const ClickAwayLi... | diff --git a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
--- a/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
+++ b/packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js
@@ -1,87 +1,58 @@... | [ClickAwayListener] Accept default prevented events
By default, ClickAwayListener ignores events that use event.preventDefault(). While this is desired in most cases, there are some cases where this should be a configurable feature.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of... | What about removing this logic? Per
https://github.com/mui-org/material-ui/blob/d30e5ae648d7b499161f4dd31da8c846d99a990e/packages/material-ui/src/Modal/Modal.js#L186-L191
I think that we could add a `allowPreventDefaultEvents` prop until we change the behavior in v5, at which point, we can remove it. Would that work f... | 2019-12-10 02:07:25+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> should render the children', 'packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: onClickAway should not be called when clicking inside', 'packages/material-ui/src/ClickAwayListene... | ['packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: onClickAway should be called when preventDefault is `true`'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 18,786 | mui__material-ui-18786 | ['18344'] | 333749d2b7dfcb7b0990fe56e17d92f41aeda369 | diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -579,7 +579,7 @@ export default fu... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -720,4 +720,26 @@ describe('<Autocompl... | [Autocomplete] Triggers change event twice with "enter"
<!-- Provide a general summary of the issue in the Title above -->
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off the following list.
-->
<!-- Checked checkbox should... | i think this problem of getOptionLabel
```
<Autocomplete
freeSolo
id="combo-box-demo"
options={top100Films}
getOptionLabel={option => option.title}
style={{ width: 300 }}
renderInput={params => (
<TextField {...params} label="Combo box" variant="outlined" fullWidth />
... | 2019-12-11 02:30:20+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: freeSolo pressing twice enter should not call onChange listener twice'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
mui/material-ui | 18,796 | mui__material-ui-18796 | ['18784'] | c4c5a03e143f1d23007a32e5fa4bbf4531bbfa33 | diff --git a/docs/pages/api/autocomplete.md b/docs/pages/api/autocomplete.md
--- a/docs/pages/api/autocomplete.md
+++ b/docs/pages/api/autocomplete.md
@@ -57,7 +57,7 @@ You can learn more about the difference by [reading this guide](/guides/minimizi
| <span class="prop-name">noOptionsText</span> | <span class="prop-ty... | diff --git a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
--- a/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
+++ b/packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js
@@ -742,4 +742,41 @@ describe('<Autocompl... | [Autocomplete] Prevent onInputChange when onChange is fired
<!-- Provide a general summary of the feature in the Title above -->
I'm not really sure whether to classify this as a bug or feature request as I'm not familiar with what's actually intended here.
When `onChange` is fired, `onInputChange` is also fired,... | @Tybot204 We have a related issue in #18656 where we plan to switch the call order between `onChange` and `onInputChange`. However, your case is different from this related issue, it's about data fetching and not form validation.
In the google map demo, we hack this problem a bit as we listen for the change event on... | 2019-12-11 22:05:26+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 && yarn install && yarn add -D -W --ignore-engines @types/prop-types @types/react-dom @types/sinon @types/chai @types/chai-dom @types/format-util
RUN echo 'var mocha = require("mocha");' > custo... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> Material-UI component API applies to root class to the root component if it has this class', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> when popup open closes the popup if Escape is pressed ', 'pack... | ['packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: onInputChange provides a reason on select reset', 'packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js-><Autocomplete /> prop: onInputChange provides a reason on input change'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/Autocomplete/Autocomplete.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js->program->function_declaration:useAutocomplete"] |
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.