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 | 11,585 | mui__material-ui-11585 | ['11584', '11584'] | 2b7cb47228766df6a02a8a8ba9ab14a37324bcad | diff --git a/docs/src/pages/guides/composition/ComponentProperty.js b/docs/src/pages/guides/composition/ComponentProperty.js
--- a/docs/src/pages/guides/composition/ComponentProperty.js
+++ b/docs/src/pages/guides/composition/ComponentProperty.js
@@ -9,7 +9,8 @@ import Divider from '@material-ui/core/Divider';
import ... | 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
@@ -527,13 +527,12 @@ describe('<ButtonBase />', () => {
describe(... | [ButtonBase] Using with Link component from react-router, enter key is not working.
- [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.
## Expected Behavior
When pre... | 2018-05-25 14:05:10+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> handleKeyDown() Keyboard accessibility for non interactive elements should ignore the link with href'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ButtonBase/ButtonBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 4 | 1 | 5 | false | false | ["docs/src/pages/guides/composition/ComponentProperty.js->program->function_declaration:ComponentProperty", "packages/material-ui/src/ButtonBase/focusVisible.js->program->function_declaration:isFocusKey", "docs/src/pages/guides/composition/ComponentProperty.js->program->function_declaration:SimpleList", "packages/mater... | |
mui/material-ui | 11,730 | mui__material-ui-11730 | ['11139'] | ef7abe8378c45a9601d7218e5b76f7567c03d8dd | diff --git a/docs/src/modules/components/withRoot.js b/docs/src/modules/components/withRoot.js
--- a/docs/src/modules/components/withRoot.js
+++ b/docs/src/modules/components/withRoot.js
@@ -79,8 +79,7 @@ const pages = [
pathname: '/layout/hidden',
},
{
- pathname: '/layout/css-in-js',
- ... | diff --git a/packages/material-ui/src/withWidth/withWidth.test.js b/packages/material-ui/src/withWidth/withWidth.test.js
--- a/packages/material-ui/src/withWidth/withWidth.test.js
+++ b/packages/material-ui/src/withWidth/withWidth.test.js
@@ -35,7 +35,6 @@ describe('withWidth', () => {
describe('prop: width', () => ... | [docs] Document withWidth utility function
<!--- Provide a general summary of the issue in the Title above -->
Would it be useful to have this function within `Dialog`'s import to be a more generic, utility function? Such as `isMobileScreen` or `isFullScreen` that can safely be wrapped around any component? I often fi... | @Auchindoun The implementation of `withMobileDialog` is pretty empty.
https://github.com/mui-org/material-ui/blob/1839c0804fd9671f42cf5bc09160869afc9e08c4/packages/material-ui/src/Dialog/withMobileDialog.js#L10-L22
It's a sugar wrapper on top of `withWidth`. I agree, we should be documenting it. | 2018-06-05 21:47:38+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/withWidth/withWidth.test.js->withWidth server side rendering should not render the children as the width is unknown', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth option: withTheme should forward the theme', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth ... | ['packages/material-ui/src/withWidth/withWidth.test.js->withWidth width computation should work as expected', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth option: initialWidth should work as expected', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth option: noSSR should work as expe... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/withWidth/withWidth.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 5 | 1 | 6 | false | false | ["packages/material-ui/src/withWidth/withWidth.js->program->class_declaration:WithWidth->method_definition:getWidth", "packages/material-ui/src/withWidth/withWidth.js->program->class_declaration:WithWidth->method_definition:componentDidMount", "packages/material-ui/src/withWidth/withWidth.js->program->class_declaration... |
mui/material-ui | 11,789 | mui__material-ui-11789 | ['11754'] | ea529824ae4e2d02ce67cf39478c98b1af7b060e | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -27,7 +27,7 @@ module.exports = [
name: 'The size of all the modules of material-ui.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.7 KB',
+ limit: '94.8 KB',
},
{
name: ... | 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
@@ -1,5 +1,4 @@
import React from 'react';
-import { spy } from ... | Focus shifted to input element when I click on link in helptext
I added an Input field and in its helptext, I added an link for my documentation. When I click on that link, the focus shifted to input element. It should not happen as I didn't click on input field.
<!-- Checked checkbox should look like this: [x] -->... | null | 2018-06-09 18:13:38+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Input/Input.test.js-><Input /> controlled should considered [] as controlled', 'packages/material-ui/src/Input/Input.test.js-><Input /> mount should be able to access the native textarea', 'packages/material-ui/src/Input/Input.test.js-><Input /> isFilled is true for SSR defaultValue 0', 'pack... | ['packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> prop: onFocus should work', 'packages/material-ui/src/Input/Input.test.js-><Input /> with muiFormControl context callbacks should fire the onFocus muiFormControl', 'packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> prop: onBlur sh... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/FormControl/FormControl.test.js packages/material-ui/src/internal/SwitchBase.test.js packages/material-ui/src/Input/Input.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 2 | 3 | 5 | false | false | ["packages/material-ui/src/FormControl/FormControl.js->program->class_declaration:FormControl->method_definition:render", "packages/material-ui/src/internal/SwitchBase.js->program->class_declaration:SwitchBase->method_definition:render", "packages/material-ui/src/Input/Input.js->program->class_declaration:Input", "pack... |
mui/material-ui | 11,793 | mui__material-ui-11793 | ['11751'] | a35b212a806cf2b7e2d515ef5e653780f68c9a78 | diff --git a/packages/material-ui/src/RadioGroup/RadioGroup.js b/packages/material-ui/src/RadioGroup/RadioGroup.js
--- a/packages/material-ui/src/RadioGroup/RadioGroup.js
+++ b/packages/material-ui/src/RadioGroup/RadioGroup.js
@@ -3,7 +3,7 @@
import React from 'react';
import PropTypes from 'prop-types';
import Form... | diff --git a/packages/material-ui/src/RadioGroup/RadioGroup.test.js b/packages/material-ui/src/RadioGroup/RadioGroup.test.js
--- a/packages/material-ui/src/RadioGroup/RadioGroup.test.js
+++ b/packages/material-ui/src/RadioGroup/RadioGroup.test.js
@@ -117,35 +117,51 @@ describe('<RadioGroup />', () => {
);
});
... | Can't trigger TextField onChange() when TextField is inside RadioGroup
- [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.
## Expected Behavior
Sometimes you need t... | null | 2018-06-09 22:39:51+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> should accept invalid child', 'packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> prop: onChange should not fire onChange if not checked', 'packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> imperative focus... | ['packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> prop: onChange should chain the onChange property'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/RadioGroup/RadioGroup.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/utils/helpers.js->program->function_declaration:createChainedFunction", "packages/material-ui/src/RadioGroup/RadioGroup.js->program->class_declaration:RadioGroup->method_definition:render"] |
mui/material-ui | 11,825 | mui__material-ui-11825 | ['8379'] | 98168a2c749d8da2376d6a997145e3622df71bff | diff --git a/packages/material-ui/src/Tabs/Tabs.js b/packages/material-ui/src/Tabs/Tabs.js
--- a/packages/material-ui/src/Tabs/Tabs.js
+++ b/packages/material-ui/src/Tabs/Tabs.js
@@ -143,7 +143,7 @@ class Tabs extends React.Component {
const children = this.tabs.children[0].children;
if (children.length... | 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
@@ -246,6 +246,19 @@ describe('<Tabs />', () => {
);
});
+ it('should accept any value as selected... | [Tabs] Tab indicator in Tabs behaves wrong when tabs are dynamically changed
- [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
The tab indicator must always show the selected tab
## Current Behavio... | We might want to change this logic:
https://github.com/callemall/material-ui/blob/438dd7f7fc14f504f0e385fef1719ee6674fa3ca/src/Tabs/Tabs.js#L164-L167
@oliviertassinari Would it be too bad performance to remove the if statement arround :-) ?
I would really like to contribute but is relativly new in the open source w... | 2018-06-12 06:22:54+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: value indicator should let the selected <Tab /> render the indicator', '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... | ['packages/material-ui/src/Tabs/Tabs.test.js-><Tabs /> prop: value indicator should accept any value as selected tab value'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tabs/Tabs.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/Tabs/Tabs.js->program->class_declaration:Tabs", "packages/material-ui/src/Tabs/Tabs.js->program->class_declaration:Tabs->method_definition:render"] |
mui/material-ui | 11,858 | mui__material-ui-11858 | ['11834'] | 4acfb8da9fb5fc258871aa5a55788fa37208babc | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -27,7 +27,7 @@ module.exports = [
name: 'The size of all the modules of material-ui.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.9 KB',
+ limit: '95.0 KB',
},
{
name: ... | diff --git a/packages/material-ui/src/ListItemText/ListItemText.test.js b/packages/material-ui/src/ListItemText/ListItemText.test.js
--- a/packages/material-ui/src/ListItemText/ListItemText.test.js
+++ b/packages/material-ui/src/ListItemText/ListItemText.test.js
@@ -213,4 +213,27 @@ describe('<ListItemText />', () => {... | Getting ListItemText to inherit color is a pain
<!--- 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 lo... | > I have to do:
You also have to add `disableTypography `.
Ah, I hadn't even tried, I was just guessing. So it takes even more text to do.
As a side note, I wish there were some magic way to reference the JSS class name for the `ListItemText` and `Typography` within the styles for my sidebar...then I could overrid... | 2018-06-14 14:37:15+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> prop: primary should use the children prop as primary node', 'packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> should render with the user and root classes', 'packages/material-ui/src/ListItemText/ListItemText.tes... | ['packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> should pass secondaryTypographyProps to secondary Typography component', 'packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> should pass primaryTypographyProps to primary Typography component'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ListItemText/ListItemText.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/ListItemText/ListItemText.js->program->function_declaration:ListItemText"] |
mui/material-ui | 11,891 | mui__material-ui-11891 | ['10643'] | 601e9a4b0a9956c2dce6ed550ee3288497897f85 | diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,62 @@ Material-UI strictly follows [Semantic Versioning 2.0.0](http://semver.org/).
- Weekly release: patch or minor version at the end of every week for routine bugfix or new features (anytime for urgent bugfix).
- Major versio... | 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
@@ -243,16 +243,20 @@ describe('<SelectInput />', () => {
describe('prop: autoWidt... | Animate Tab and selection box problem
## Expected Behavior
I am using the tab with "react-swipeable-views" animation like the example https://material-ui.com/demos/tabs/#fixed-tabs. And I use the selection box like the example https://material-ui.com/demos/selects/#simple-select under the tab content.
I expect the ... | Related to https://github.com/oliviertassinari/react-swipeable-views/issues/417
Problem solved by downgrading the react-swipeable-views version to 0.12.4
with 0.12.4 problem gone
The root of the issue is in this line.
https://github.com/mui-org/material-ui/blob/e199c9fb70622b8a2b4bf42ff6af22029ada2ea6/src/Select/Sele... | 2018-06-17 21:16:00+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: displayEmpty should display the selected item even if its value is empty', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: MenuProps should be able to override PaperProps minWidth', 'packages/material-ui/src/Select/... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: autoWidth should not take the anchor width into account'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 2 | 1 | 3 | false | false | ["packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput->method_definition:shouldComponentUpdate", "packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput", "packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput->method_de... |
mui/material-ui | 11,941 | mui__material-ui-11941 | ['11932'] | 360477432feee46a4e19a3e58e173b37fac990b6 | diff --git a/docs/src/pages/demos/buttons/FloatingActionButtons.js b/docs/src/pages/demos/buttons/FloatingActionButtons.js
--- a/docs/src/pages/demos/buttons/FloatingActionButtons.js
+++ b/docs/src/pages/demos/buttons/FloatingActionButtons.js
@@ -5,11 +5,15 @@ import Button from '@material-ui/core/Button';
import AddI... | 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
@@ -28,9 +28,9 @@ describe('<Button />', () => {
it('should render with the root & flat classes but ... | [Button] Multiple variant styles being applied
- [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.
## Expected Behavior
When a variant is chosen, e.g. `outlined`, ot... | @murtyjones An outlined button is a flat button with a border, so this is an efficient reuse of styles, rather than duplicating them.
We could:
- Duplicate the styles
- Rename the flat style to reflect its dual purpose (breaking change)
- Leave it as is (I haven't gone hunting, but I'm pretty sure we have oth... | 2018-06-21 17:34:51+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Button/Button.test.js-><Button /> should render a raised primary button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render the custom className and the root class', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render an secondary floating action ... | ['packages/material-ui/src/styles/MuiThemeProvider.test.js-><MuiThemeProvider /> server side should be able to extract the styles', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render an outlined button', 'packages/material-ui/src/Button/Button.test.js-><Button /> should render a primary outlined ... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Button/Button.test.js packages/material-ui/src/styles/MuiThemeProvider.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/src/pages/demos/buttons/FloatingActionButtons.js->program->function_declaration:FloatingActionButtons", "packages/material-ui/src/Button/Button.js->program->function_declaration:Button"] |
mui/material-ui | 11,987 | mui__material-ui-11987 | ['4489'] | 09896d42e6206984a54272cc2059c49a7aa9d54f | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -27,7 +27,7 @@ module.exports = [
name: 'The size of all the modules of material-ui.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.8 KB',
+ limit: '94.9 KB',
},
{
name: ... | diff --git a/packages/material-ui/src/SvgIcon/SvgIcon.test.js b/packages/material-ui/src/SvgIcon/SvgIcon.test.js
--- a/packages/material-ui/src/SvgIcon/SvgIcon.test.js
+++ b/packages/material-ui/src/SvgIcon/SvgIcon.test.js
@@ -2,20 +2,26 @@
import React from 'react';
import { assert } from 'chai';
-import { createS... | SVG Icons: Unable to Supply <defs> Element
Although the SVG font icons support a `children` prop, I am unable to pass in a `defs` element to define a custom linear gradient. I.e.:
```jsx
import Stars from 'material-ui/svg-icons/action/stars';
<Stars
children={
<defs... | @joncursi The pre-built icons don't currently support children, as the path for the icon itself is the `SvgIcon` children.
```jsx
import React from 'react';
import pure from 'recompose/pure';
import SvgIcon from '../../SvgIcon';
let ActionStars = (props) => (
<SvgIcon {...props}>
<path d="M11.99 2C6.47... | 2018-06-26 21:45:58+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/SvgIcon/SvgIcon.test.js-><SvgIcon /> prop: color should render with the error color', 'packages/material-ui/src/SvgIcon/SvgIcon.test.js-><SvgIcon /> prop: color should render with the primary class', 'packages/material-ui/src/SvgIcon/SvgIcon.test.js-><SvgIcon /> prop: color should render with... | ['packages/material-ui/src/SvgIcon/SvgIcon.test.js-><SvgIcon /> prop: component should render component before path'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/SvgIcon/SvgIcon.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/SvgIcon/SvgIcon.js->program->function_declaration:SvgIcon", "docs/src/pages/style/icons/SvgIcons.js->program->function_declaration:SvgIcons"] |
mui/material-ui | 12,002 | mui__material-ui-12002 | ['11946'] | 5798bf644981a22459469e8bfb5d50f5287ab560 | 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
@@ -133,19 +133,24 @@ class Snackbar extends React.Component {
}
// Timer that controls delay before ... | 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
@@ -275,6 +275,29 @@ describe('<Snackbar />', () => {
assert.strictEqual(handleClo... | [Snackbar] resumeHideDuration short-circuits on 0 milliseconds
- [x] I have searched the issues of this repository and believe that this is not a duplicate.
## Expected Behavior
When passing a value of `0` into the resumeHideDuration prop of the Snackbar component, the Snackbar will immediately fire `onClose` fol... | @benz2012 You are right, we need to fix this line: https://github.com/mui-org/material-ui/blob/dce7801ffc1187137301d84bc367e7b8880e522e/packages/material-ui/src/Snackbar/Snackbar.js#L146
Something like this should do it:
```diff
-}, autoHideDuration || this.props.autoHideDuration || 0);
+}, autoHideDuration !== nu... | 2018-06-28 15:53:17+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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: resumeHideDuration should call onClose immediately after user interaction when 0'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Snackbar/Snackbar.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/Snackbar/Snackbar.js->program->class_declaration:Snackbar", "packages/material-ui/src/Snackbar/Snackbar.js->program->class_declaration:Snackbar->method_definition:setAutoHideTimer"] |
mui/material-ui | 12,026 | mui__material-ui-12026 | ['12001'] | c92d9f2931c0f97ab4a4963812ce01aaaa5b3efa | diff --git a/packages/material-ui/src/StepIcon/StepIcon.d.ts b/packages/material-ui/src/StepIcon/StepIcon.d.ts
--- a/packages/material-ui/src/StepIcon/StepIcon.d.ts
+++ b/packages/material-ui/src/StepIcon/StepIcon.d.ts
@@ -9,7 +9,7 @@ export interface StepIconProps
icon: React.ReactNode;
}
-export type StepIconCl... | diff --git a/packages/material-ui/src/StepIcon/StepIcon.test.js b/packages/material-ui/src/StepIcon/StepIcon.test.js
--- a/packages/material-ui/src/StepIcon/StepIcon.test.js
+++ b/packages/material-ui/src/StepIcon/StepIcon.test.js
@@ -3,8 +3,8 @@ import { assert } from 'chai';
import CheckCircle from '../internal/svg-... | How to apply a custom className to StepPositionIcon?
I am trying to customize a vertical stepper like this:
```
const theme = createMuiTheme({
overrides: {
MuiStepConnector: {
lineVertical: {
minHeight: '',
}
},
MuiStepContent: {
last: {
borderLeft: ''
... | @bousejin The `StepPositionIcon` component is private, it might change in the future. You can't target it directly:
https://github.com/mui-org/material-ui/blob/5798bf644981a22459469e8bfb5d50f5287ab560/packages/material-ui/src/StepIcon/StepPositionIcon.js#L19
@oliviertassinari Thank you so much. I have some card inside... | 2018-07-01 19:26:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/StepIcon/StepIcon.test.js-><StepIcon /> renders <Warning> when error occured', 'packages/material-ui/src/StepIcon/StepIcon.test.js-><StepIcon /> renders the custom icon', 'packages/material-ui/src/StepIcon/StepIcon.test.js-><StepIcon /> renders <CheckCircle> when completed'] | ['packages/material-ui/src/StepIcon/StepIcon.test.js-><StepIcon /> renders a <SvgIcon>', 'packages/material-ui/src/StepIcon/StepIcon.test.js-><StepIcon /> contains text "3" when position is "3"'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/StepIcon/StepIcon.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/StepIcon/StepIcon.js->program->function_declaration:StepIcon"] |
mui/material-ui | 12,075 | mui__material-ui-12075 | ['11619'] | 142e61ce746ddce81c5b763ff74ad8f1c0e3a6cf | diff --git a/docs/src/pages/demos/app-bar/ButtonAppBar.js b/docs/src/pages/demos/app-bar/ButtonAppBar.js
--- a/docs/src/pages/demos/app-bar/ButtonAppBar.js
+++ b/docs/src/pages/demos/app-bar/ButtonAppBar.js
@@ -13,7 +13,7 @@ const styles = {
flexGrow: 1,
},
flex: {
- flex: 1,
+ flexGrow: 1,
},
me... | diff --git a/packages/material-ui/src/Toolbar/Toolbar.test.js b/packages/material-ui/src/Toolbar/Toolbar.test.js
--- a/packages/material-ui/src/Toolbar/Toolbar.test.js
+++ b/packages/material-ui/src/Toolbar/Toolbar.test.js
@@ -29,10 +29,12 @@ describe('<Toolbar />', () => {
it('should disable the gutters', () => {
... | "Dense" AppBar
Material-design defines a "dense" version of the AppBar for Desktop. It makes sense, because the AppBar is generally way too large on Desktop.
The `<AppBar>` component misses this `dense` prop.
![2018-05-29_0103](https://user-images.githubusercontent.com/99944/40631352-1e35943a-62dc-11e8-9cf6-e2e41... | I'm wondering if the prop should only be available only to the AppBar or also for the Toolbar component
Is anyone working on this feature? i'd love to work on it.
@adeelibr it seems nobody does, feel free to give it a go!
@fzaninotto I am going to start working on it from tomorrow. I am already working on this table th... | 2018-07-06 19:58:38+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Toolbar/Toolbar.test.js-><Toolbar /> should disable the gutters', 'packages/material-ui/src/Toolbar/Toolbar.test.js-><Toolbar /> should render a div', 'packages/material-ui/src/Toolbar/Toolbar.test.js-><Toolbar /> should render with the user, root and gutters classes'] | ['packages/material-ui/src/Toolbar/Toolbar.test.js-><Toolbar /> should condense itself'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Toolbar/Toolbar.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 5 | 0 | 5 | false | false | ["pages/demos/app-bar.js->program->function_declaration:Page", "packages/material-ui/src/Toolbar/Toolbar.js->program->function_declaration:Toolbar", "docs/src/pages/demos/app-bar/MenuAppBar.js->program->class_declaration:MenuAppBar->method_definition:render", "docs/src/pages/demos/app-bar/SimpleAppBar.js->program->func... |
mui/material-ui | 12,100 | mui__material-ui-12100 | ['12031'] | 8e4b2528d94e0d0ad73c7674a37d882398df72c7 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -21,13 +21,13 @@ module.exports = [
name: 'The initial cost people pay for using one component',
webpack: true,
path: 'packages/material-ui/build/Paper/index.js',
- limit: '17.6 KB',
+ limit: '17.8 KB',
},
... | 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
@@ -77,6 +77,9 @@ describe('createMuiTheme', () => {
MuiButtonBa... | Prototypes are lost when set as theme defaults
- [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.
## Expected Behavior
Default props in a theme keep their prototype... | > The prototype in theme props is removed due to the use of deepmerge.
@remcohaszing Looking at the options of deepmerge, I think that we should be ignoring non "plain object" : https://github.com/KyleAMathews/deepmerge#ismergeableobject.
This implementation is intereseting: https://github.com/jonschlinkert/is-plai... | 2018-07-09 23:37:47+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 props should have the props as expected'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 12,168 | mui__material-ui-12168 | ['12154'] | 18c87b07ce0645954d0f6202896fe6a346446344 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -27,7 +27,7 @@ module.exports = [
name: 'The size of all the modules of material-ui.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.7 KB',
+ limit: '94.8 KB',
},
{
name: ... | 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
@@ -20,7 +20,7 @@ describe('<Tooltip />', () => {
};
before(() => {
- shallow = create... | [Tooltip] Bugs in version 1.4.0
- [x] This is a v1.x issue.
- [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.
## Bugs
- Double tooltip: when enterDelay is higher this bug is most visible.
- Cut tooltip: when the browser s... | > when enterDelay is higher this bug is most visible.
Can it be noticed with `enterDelay={0}`?
@oliviertassinari Yes, with enterDelay={0} is noticed, but it is more difficult to reproduce.
With this example, FormControlLabel map enterDelay={0}, sometimes the other tooltip is visible.
![image](https://user-images.g... | 2018-07-16 21:57:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> should render the corr... | ['packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> should close when the interaction is over'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 2 | 3 | false | false | ["packages/material-ui/src/Tooltip/Tooltip.js->program->class_declaration:Tooltip->method_definition:componentDidMount", "packages/material-ui/src/Tooltip/Tooltip.js->program->class_declaration:Tooltip", "packages/material-ui/src/Popper/Popper.js->program->class_declaration:Popper"] |
mui/material-ui | 12,202 | mui__material-ui-12202 | ['12188'] | a207808404a703d1ea2b03ac510343be6404b166 | diff --git a/packages/material-ui/src/ButtonBase/createRippleHandler.js b/packages/material-ui/src/ButtonBase/createRippleHandler.js
--- a/packages/material-ui/src/ButtonBase/createRippleHandler.js
+++ b/packages/material-ui/src/ButtonBase/createRippleHandler.js
@@ -6,6 +6,7 @@ function createRippleHandler(instance, ev... | 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
@@ -249,24 +249,19 @@ describe('<Modal />', () => {
describe('handleDocumentKeyDown()', () => {
let wrapp... | [Drawer] Close persistent drawer on Escape keydown
Hi!
I want to make right `persistent` drawer (like in [three pane interfaces](https://en.wikipedia.org/wiki/Three-pane_interface)). Also I want to close right pane by <kbd >Escape</kbd> pressed. But this keypress works only for `temporary` drawers based on `Modal` c... | @mctep I would suggest you to use a custom modalManager instance, providing it to all the modals you are using (you can use theme for that). Then, you can use the `isTopModal()` method to know if you have to handle the <kbd>Escape</kbd> event.
Also, I'm wondering if we should be checking `event.defaultPrevented` in ... | 2018-07-19 22:49:47+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should render a backdrop component into the portal before the modal content', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleDocumentKeyDown() should... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleDocumentKeyDown() should not be call when defaultPrevented'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/ButtonBase/createRippleHandler.js->program->function_declaration:createRippleHandler", "packages/material-ui/src/Modal/Modal.js->program->class_declaration:Modal"] |
mui/material-ui | 12,218 | mui__material-ui-12218 | ['12198'] | 3c6fa7735102511079c4ab3ca859d39e113db06a | diff --git a/docs/src/pages/utils/popper/PositionedPopper.js b/docs/src/pages/utils/popper/PositionedPopper.js
--- a/docs/src/pages/utils/popper/PositionedPopper.js
+++ b/docs/src/pages/utils/popper/PositionedPopper.js
@@ -28,7 +28,7 @@ class PositionedPopper extends React.Component {
const { currentTarget } = eve... | 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
@@ -106,6 +106,22 @@ describe('<Popper />', () => {
wrapper.setProps({ open: false });
asse... | [Popper] Weird Behavior While Hiding it.
<!--- Provide a general summary of the issue in the Title above -->
I'm using the new Popper component that released in 1.4.0. While closing the menu there's some weird behavior happening and I believe that is happening because of the transition from position absolute and stati... | Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. [This **codesandbox.io** template](https://codesandbox.io/s/github/callemall/material-ui/tree/master/examples/create-react-app) _may_ be a good starting point. Thank you! | 2018-07-20 21:58:57+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> mo... | ['packages/material-ui/src/Popper/Popper.test.js-><Popper /> prop: transition should work'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popper/Popper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 2 | 2 | 4 | false | false | ["packages/material-ui/src/Popper/Popper.js->program->class_declaration:Popper->method_definition:render", "docs/src/pages/utils/popper/PositionedPopper.js->program->class_declaration:PositionedPopper", "packages/material-ui/src/Popper/Popper.js->program->class_declaration:Popper->method_definition:componentDidUpdate",... |
mui/material-ui | 12,236 | mui__material-ui-12236 | ['12216'] | 18aa6293ad8b67dc8a323db19117c93efa966c7c | diff --git a/packages/material-ui/src/styles/withTheme.d.ts b/packages/material-ui/src/styles/withTheme.d.ts
--- a/packages/material-ui/src/styles/withTheme.d.ts
+++ b/packages/material-ui/src/styles/withTheme.d.ts
@@ -3,6 +3,7 @@ import { ConsistentWith } from '..';
export interface WithTheme {
theme: Theme;
+ ... | diff --git a/packages/material-ui/src/styles/withTheme.test.js b/packages/material-ui/src/styles/withTheme.test.js
--- a/packages/material-ui/src/styles/withTheme.test.js
+++ b/packages/material-ui/src/styles/withTheme.test.js
@@ -1,11 +1,18 @@
import React from 'react';
import { assert } from 'chai';
+import { spy }... | [withWidth] Add innerRef property
<!--- 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 checkbox should look like this... | @itelo You can use the [RootRef](https://material-ui.com/api/root-ref/) component for this use case. Regarding the `innerRef` property. My hope is that it can be legacy with #10825.
The `withTheme` higher-order component could take advantage of it too.
@oliviertassinari can you give an example of how to use the RootRef... | 2018-07-22 15:42:00+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/withWidth/withWidth.test.js->withWidth server side rendering should not render the children as the width is unknown', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth option: withTheme should forward the theme', 'packages/material-ui/src/withWidth/withWidth.test.js->withWidth ... | ['packages/material-ui/src/withWidth/withWidth.test.js->withWidth prop: innerRef should provide a ref on the inner component', 'packages/material-ui/src/styles/withTheme.test.js->withTheme prop: innerRef should provide a ref on the inner component'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/withWidth/withWidth.test.js packages/material-ui/src/styles/withTheme.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/withWidth/withWidth.js->program->class_declaration:WithWidth->method_definition:render", "packages/material-ui/src/styles/withTheme.js->program->class_declaration:WithTheme->method_definition:render"] |
mui/material-ui | 12,303 | mui__material-ui-12303 | ['11618'] | f432f8a733514b3fa83718102d78f1311cb19de0 | diff --git a/docs/src/pages/demos/selection-controls/CheckboxesGroup.js b/docs/src/pages/demos/selection-controls/CheckboxesGroup.js
--- a/docs/src/pages/demos/selection-controls/CheckboxesGroup.js
+++ b/docs/src/pages/demos/selection-controls/CheckboxesGroup.js
@@ -1,4 +1,6 @@
import React from 'react';
+import PropT... | diff --git a/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js b/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js
--- a/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js
+++ b/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js
@@ -55,6 +55,15 @@ descri... | How to position Switch label to the left of the switch?
- [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 examples here](https://material-ui.com/demos/selectio... | `FormControlLabel` wasn't designed with this use case in mind. You would need to write custom CSS to get this behavior.
I have added the `waiting for users upvotes` tag. I'm closing the issue as I'm not sure people are looking for such abstraction. So please upvote this issue if you are. We will prioritize our effort b... | 2018-07-27 17:03:10+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> with muiFormControl context disabled should have the disabled class', 'packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: disabled should disable everything 1', 'packages/material-ui/sr... | ['packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: labelPlacement should disable have the `start` class'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/FormControlLabel/FormControlLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 3 | 1 | 4 | false | false | ["packages/material-ui/src/FormControlLabel/FormControlLabel.js->program->function_declaration:FormControlLabel", "docs/src/pages/demos/selection-controls/CheckboxesGroup.js->program->class_declaration:CheckboxesGroup", "docs/src/pages/demos/selection-controls/RadioButtonsGroup.js->program->class_declaration:RadioButto... |
mui/material-ui | 12,378 | mui__material-ui-12378 | ['12370'] | 857928e6c0c82fad08d90aad6d7bc60390d0f4c1 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -27,7 +27,7 @@ module.exports = [
name: 'The size of all the modules of material-ui.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '95.5 KB',
+ limit: '95.6 KB',
},
{
name: ... | 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
@@ -24,25 +24,40 @@ describe('<Chip />', () => {
});
describe('text only', () => {
- let wrapper;
-
- befor... | Chip missing color prop
<!--- 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 checkbox should look like this: [x] -->
... | @itelo Could you provide more detail. What would be the final output? I'm not sure I understand the use case.
something like that
| 2018-08-02 12:53:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> prop: deleteIcon should render a default icon', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> reacts to keyboard chip escape should unfocus when a esc ke... | ['packages/material-ui/src/Chip/Chip.test.js-><Chip /> deletable Avatar chip should render with the root, deletable and avatar primary classes', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> text only should render with the root and the secondary class', 'packages/material-ui/src/Chip/Chip.test.js-><Chip /> pro... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 3 | 0 | 3 | false | false | ["docs/src/pages/demos/chips/Chips.js->program->function_declaration:Chips", "pages/demos/chips.js->program->function_declaration:Page", "packages/material-ui/src/Chip/Chip.js->program->class_declaration:Chip->method_definition:render"] |
mui/material-ui | 12,389 | mui__material-ui-12389 | ['12275'] | 8013fdd36d40980ebb8f116f20e2843b781c0c39 | diff --git a/packages/material-ui/src/styles/createGenerateClassName.js b/packages/material-ui/src/styles/createGenerateClassName.js
--- a/packages/material-ui/src/styles/createGenerateClassName.js
+++ b/packages/material-ui/src/styles/createGenerateClassName.js
@@ -56,14 +56,13 @@ export default function createGenerat... | diff --git a/packages/material-ui/src/styles/createGenerateClassName.test.js b/packages/material-ui/src/styles/createGenerateClassName.test.js
--- a/packages/material-ui/src/styles/createGenerateClassName.test.js
+++ b/packages/material-ui/src/styles/createGenerateClassName.test.js
@@ -58,12 +58,13 @@ describe('createG... | dangerouslyUseGlobalCSS not working
<!--- Provide a general summary of the issue in the Title above -->
I did a little debugging to figure out why `dangerouslyUseGlobalCSS` is not working, and it seems that `styleSheet.options.classNamePrefix` is undefined. My app was created with create-react-app, so this might be a ... | @grigored Please provide a full reproduction test case. This would help a lot 👷 .
A repository would be perfect. Thank you!
@oliviertassinari Thanks for the quick reply. Here's a sample repo to demonstrate the problem: [https://github.com/grigored/dangerouslyUseGlobalCS](https://github.com/grigored/dangerouslyUseGlob... | 2018-08-02 19:49:23+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/styles/createGenerateClassName.test.js->createGenerateClassName should escape parenthesis', 'packages/material-ui/src/styles/createGenerateClassName.test.js->createGenerateClassName formatting production should warn', 'packages/material-ui/src/styles/createGenerateClassName.test.js->createGen... | ['packages/material-ui/src/styles/createGenerateClassName.test.js->createGenerateClassName options: dangerouslyUseGlobalCSS should use a global class name'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/styles/createGenerateClassName.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/styles/createGenerateClassName.js->program->function_declaration:createGenerateClassName"] |
mui/material-ui | 12,394 | mui__material-ui-12394 | ['12289'] | 809f0758f629564ab6309665a8534c548bc697b1 | 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
@@ -160,11 +160,11 @@ class Tooltip extends React.Component {
}
}
- if (event.type === 'mouseenter')... | 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
@@ -64,7 +64,7 @@ describe('<Tooltip />', () => {
wrapper.instance().childrenRef = document.... | [Tooltip] Mousing over a tooltip that covers another tooltip element will prevent the second Tooltip from opening
If I mouse over an element that has a tooltip, and that tooltip appears over a second element that has a tooltip, then I mouse over the first element's tooltip, the first element's tooltip fades out, but th... | @CharlesStover I have found a workaround. We need to use the `mouseover` event over the `mouseenter` event.
https://github.com/mui-org/material-ui/blob/ca6919db8911cd27080135ea6d823e7c0df73ce9/packages/material-ui/src/Tooltip/Tooltip.js#L303
Is this something you want to work on? :)
@oliviertassinari sandbox here ht... | 2018-08-03 00:50:15+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> should respond to external events', 'packages/material-ui/src/Tooltip/Tooltip.test.js-><Tooltip /> should be controllable'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/Tooltip/Tooltip.js->program->class_declaration:Tooltip->method_definition:render", "packages/material-ui/src/Tooltip/Tooltip.js->program->class_declaration:Tooltip"] |
mui/material-ui | 12,402 | mui__material-ui-12402 | ['12391'] | 809f0758f629564ab6309665a8534c548bc697b1 | 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
@@ -129,6 +129,16 @@ export default function createPalette(palette: Object) {
if (!color.mai... | 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
@@ -361,4 +361,13 @@ describe('createPalette()', () => {
/Material-UI:... | passing empty object to override `palette` theme sub-object throws error
<!-- Checked checkbox should look like this: [x] -->
- [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... | @bmueller-sykes Sorry, I don't understand. Could you explain in more detail your use case for writing such code:
```jsx
export const sykesTheme = createMuiTheme({
palette: {
primary: {}
}
})
```
Sure! The default theme is pretty complicated, and I doubt a developer is likely to remember each and every pie... | 2018-08-03 19:43:19+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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() should calculate light and dark colors if not provided', 'packages/material-ui/src/styles/createPalette.test.js->cr... | ['packages/material-ui/src/styles/createPalette.test.js->createPalette() augmentColor should throw when the input is invalid'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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->function_declaration:augmentColor"] |
mui/material-ui | 12,406 | mui__material-ui-12406 | ['12247'] | cbc6828c93df70b897366f0c6d0b17da681d1b89 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -27,7 +27,7 @@ module.exports = [
name: 'The size of all the modules of material-ui.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '95.7 KB',
+ limit: '95.8 KB',
},
{
name: ... | diff --git a/packages/material-ui/src/Input/Textarea.test.js b/packages/material-ui/src/Input/Textarea.test.js
--- a/packages/material-ui/src/Input/Textarea.test.js
+++ b/packages/material-ui/src/Input/Textarea.test.js
@@ -28,7 +28,7 @@ describe('<Textarea />', () => {
let mount;
before(() => {
- shallow = c... | 1.4.1 Texfield multiline jest snapshot tests broken
When upgrading to 1.4.1 all our snapshot tests including a `<TextField multiline />` are broken due to `Error: Uncaught [TypeError: Cannot read property 'scrollHeight' of null]`.
We had similar issues in the past which were related to refs + react-test-renderer, but ... | @sakulstra I have removed some defensive checks that looks very much like dead code to me in #12238 and #12239. I doubt the root of the issue is on Material-UI. The component can be mounted just fine on a browser environment.
I am having this issue as well. The issue is caused by the `syncHeightWithShadow` function ins... | 2018-08-04 01:10:21+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Input/Textarea.test.js-><Textarea /> height behavior should respect the rowsMax property', 'packages/material-ui/src/Input/Textarea.test.js-><Textarea /> height behavior should update the height when the value change', 'packages/material-ui/src/Input/Textarea.test.js-><Textarea /> prop: texta... | ['packages/material-ui/src/Input/Textarea.test.js-><Textarea /> should change its height when the height of its shadows changes', 'packages/material-ui/src/Input/Textarea.test.js-><Textarea /> prop: onChange should be call the callback', 'packages/material-ui/src/Input/Textarea.test.js-><Textarea /> should render 3 tex... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Input/Textarea.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Input/Textarea.js->program->class_declaration:Textarea->method_definition:syncHeightWithShadow"] |
mui/material-ui | 12,415 | mui__material-ui-12415 | ['12162'] | b0cfad4daccea68f765917b9e00cfd151d9dbd23 | diff --git a/packages/material-ui/src/Table/Table.js b/packages/material-ui/src/Table/Table.js
--- a/packages/material-ui/src/Table/Table.js
+++ b/packages/material-ui/src/Table/Table.js
@@ -18,7 +18,9 @@ class Table extends React.Component {
getChildContext() {
// eslint-disable-line class-methods-use-this
... | 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
@@ -25,7 +25,7 @@ describe('<Table />', () => {
it('should spread custom props on the root node', () => {
... | [Table] Add padding attribute to the component
The ``padding`` attribute in the ``TableCell`` is useful but it's kind of a pain in the ass to add it to every cell (or cell generation loops) if we want the whole ``Table`` to be ``dense`` for example.
I think that it would be great to have ``<Table padding="dense">...... | @HRK44 I agree, we can solve this pain point. | 2018-08-05 06:42:38+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Table/Table.test.js-><Table /> should render a div', 'packages/material-ui/src/TableBody/TableBody.test.js-><TableBody /> should render with the user and root class', 'packages/material-ui/src/TableHead/TableHead.test.js-><TableHead /> should render with the user and root class', 'packages/ma... | ['packages/material-ui/src/Table/Table.test.js-><Table /> should define table in the child context', 'packages/material-ui/src/TableRow/TableRow.test.js-><TableRow /> should render with the head class when in the context of a table head', 'packages/material-ui/src/TableCell/TableCell.test.js-><TableCell /> should rende... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TableCell/TableCell.test.js packages/material-ui/src/TableBody/TableBody.test.js packages/material-ui/src/TableHead/TableHead.test.js packages/material-ui/src/TableRow/TableRow.test.js packages/material-ui/src/Tabl... | Feature | false | true | false | false | 6 | 0 | 6 | false | false | ["packages/material-ui/src/Table/Table.js->program->class_declaration:Table->method_definition:getChildContext", "packages/material-ui/src/TableRow/TableRow.js->program->function_declaration:TableRow", "packages/material-ui/src/TableCell/TableCell.js->program->function_declaration:TableCell", "packages/material-ui/src/... |
mui/material-ui | 12,467 | mui__material-ui-12467 | ['12204'] | 8610f8705dea228c1385c030cf279932d84a63d8 | 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
@@ -108,6 +108,9 @@ class SelectInput extends React.Component {
}
if (this.props.onBlur) {
+ ... | 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
@@ -174,6 +174,21 @@ describe('<SelectInput />', () => {
assert.strictEqual(ha... | [Select] onBlur event target
There is some mismatch with [Select] events.
```javascript
<Select
onChange={console.log}
onBlur={console.log}
>
{options}
</Select>
```
In this case, both events are fired, but onChange has ```event.target``` set to [Input] with appropriate attributes, but onBlur... | @Mangatt We are trying to simulate a native select. The implementation is challenging. The blur event comes from a div: https://github.com/mui-org/material-ui/blob/4bf97b52113f104174f0cd850bfc2a8fc73c2d99/packages/material-ui/src/Select/SelectInput.js#L287
Just a suggestion, wouldn't be better to pass name/value in eve... | 2018-08-10 12:05:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: displayEmpty should display the selected item even if its value is empty', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: MenuProps should be able to override PaperProps minWidth', 'packages/material-ui/src/Select/... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: onChange should pass "name" as part of the event.target for onBlur'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput"] |
mui/material-ui | 12,488 | mui__material-ui-12488 | ['12347'] | 4a61acde976f1be0e0b665bc7f6985d2e140b836 | 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
@@ -85,11 +85,6 @@ class Tooltip extends React.Component {
touchTimer = null;
- internalState = {
- hover:... | 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
@@ -99,7 +99,7 @@ describe('<Tooltip />', () => {
clock.tick(0);
assert.strictEqual(wra... | Tooltip still displayed after click on a button (surrounded by a Tooltip)
I notice something when using a tooltip with a button in it.
If tooltip is showed and then I click on the button, tooltip will not disapear until I click somewhere else on screen.
It is reproductible on your documentation.
![image](https://u... | @jkeruzec This behavior was specifically introduced to address #12131. You can disable the focus listener if you don't want such behavior.
Different people have now been complaining about this behavior. Let's revert it. | 2018-08-12 19:18:36+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> should close when the interaction is over'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Tooltip/Tooltip.js->program->class_declaration:Tooltip"] |
mui/material-ui | 12,570 | mui__material-ui-12570 | ['12563'] | 98f52f367375c6a4b96af6cc9f2d44d6e12c681a | diff --git a/docs/src/pages/demos/lists/NestedList.js b/docs/src/pages/demos/lists/NestedList.js
--- a/docs/src/pages/demos/lists/NestedList.js
+++ b/docs/src/pages/demos/lists/NestedList.js
@@ -26,7 +26,9 @@ const styles = theme => ({
});
class NestedList extends React.Component {
- state = { open: true };
+ sta... | diff --git a/packages/material-ui/src/ListSubheader/ListSubheader.test.js b/packages/material-ui/src/ListSubheader/ListSubheader.test.js
--- a/packages/material-ui/src/ListSubheader/ListSubheader.test.js
+++ b/packages/material-ui/src/ListSubheader/ListSubheader.test.js
@@ -50,4 +50,16 @@ describe('<ListSubheader />', ... | ListSubheader: disableGutters
<!--- Provide a general summary of the issue in the Title above -->
Hey Guys,
I just wanted to use a Subheader in a list with ListItems, which uses the `disableGutters` flag. But there is no `disableGutters` flag on the ListSubheader.
Is this intended behaviour or just a bug?
<!-... | @johannwagner You are right for symmetry, we should have a `disableGutters` property on the `ListSubheader` component! Do you want to work on it? :)
Yep, I would give it a try. This is going to be my first contribution, so please be gentle :smile:
@johannwagner Don't worry about that 👼 . | 2018-08-17 20:44:56+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/ListSubheader/ListSubheader.test.js-><ListSubheader /> should render a li', 'packages/material-ui/src/ListSubheader/ListSubheader.test.js-><ListSubheader /> prop: disableSticky should not display sticky class', 'packages/material-ui/src/ListSubheader/ListSubheader.test.js-><ListSubheader /> p... | ['packages/material-ui/src/ListSubheader/ListSubheader.test.js-><ListSubheader /> prop: disableGutters should display gutters class'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ListSubheader/ListSubheader.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 1 | 1 | 2 | false | false | ["docs/src/pages/demos/lists/NestedList.js->program->class_declaration:NestedList", "packages/material-ui/src/ListSubheader/ListSubheader.js->program->function_declaration:ListSubheader"] |
mui/material-ui | 12,630 | mui__material-ui-12630 | ['12618'] | 41e978a4183206375873f7852949e1a539d6fc56 | diff --git a/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts b/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts
--- a/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts
+++ b/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts
@@ -1,11 +1,13 @@
import * as React from 'react';
i... | diff --git a/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js b/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js
--- a/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js
+++ b/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js
@@ -2,6 +2,7 @@ import React from 'react'... | Custom TableSortLabel icon
<!--- Provide a general summary of the feature in the Title above -->
I would like to have an option of overriding default sort icon. I've looked to [TableSortLabel source](https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/TableSortLabel/TableSortLabel.js#L69) and d... | We can add an `IconComponent` property. Feel free to work on it :).
great, I'll work on it. | 2018-08-23 13:22:36+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/TableSortLabel/TableSortLabel.test.js-><TableSortLabel /> has an icon when given direction asc should have asc direction class', 'packages/material-ui/src/TableSortLabel/TableSortLabel.test.js-><TableSortLabel /> has an icon when given direction desc should have desc direction class', 'packag... | ['packages/material-ui/src/TableSortLabel/TableSortLabel.test.js-><TableSortLabel /> has an icon should accept a custom icon for the sort icon'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TableSortLabel/TableSortLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/TableSortLabel/TableSortLabel.js->program->function_declaration:TableSortLabel"] |
mui/material-ui | 12,816 | mui__material-ui-12816 | ['11812'] | 80019fd5ae0b0fdadce8dbea43f8ed76d5aa95e2 | diff --git a/packages/material-ui/src/Popover/Popover.js b/packages/material-ui/src/Popover/Popover.js
--- a/packages/material-ui/src/Popover/Popover.js
+++ b/packages/material-ui/src/Popover/Popover.js
@@ -124,8 +124,8 @@ class Popover extends React.Component {
// Check if the parent has requested anchoring on an... | diff --git a/packages/material-ui/src/Popover/Popover.test.js b/packages/material-ui/src/Popover/Popover.test.js
--- a/packages/material-ui/src/Popover/Popover.test.js
+++ b/packages/material-ui/src/Popover/Popover.test.js
@@ -657,7 +657,7 @@ describe('<Popover />', () => {
instance.getTransformOriginValue =... | [Popover] Centering issue with scrollable
See https://codesandbox.io/s/n9nvnqlx74 for an example.
It only breaks if the browser uses static scrollbars (not those invisible ones like on OSX)
## Expected Behavior
Popover should be properly centered
## Current Behavior
Popover is slightly offset to the right
!... | At least, the white part is centered 🙈.
Not really - I don't see it aligning on the right side 😕 | 2018-09-09 10:56:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ["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 /> paper should have a elevation prop passed down', 'packages/material-ui/src/Popover/Popover.test.js-><Popover /> positi... | ['packages/material-ui/src/Popover/Popover.test.js-><Popover /> getPositioningStyle(element) bottom > heightThreshold should transformOrigin according to marginThreshold', 'packages/material-ui/src/Popover/Popover.test.js-><Popover /> getPositioningStyle(element) right > widthThreshold should transformOrigin according ... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popover/Popover.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Popover/Popover.js->program->class_declaration:Popover"] |
mui/material-ui | 12,874 | mui__material-ui-12874 | ['12561'] | e3af9e9850c93d319b2b26f8cd77dca897b4d7f7 | diff --git a/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts b/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts
--- a/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts
+++ b/packages/material-ui/src/TableSortLabel/TableSortLabel.d.ts
@@ -7,6 +7,7 @@ export interface TableSortLabelProps
... | diff --git a/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js b/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js
--- a/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js
+++ b/packages/material-ui/src/TableSortLabel/TableSortLabel.test.js
@@ -65,13 +65,32 @@ describe('<TableSortL... | [TableSortLabel] Remove sort icon when not active
Table sort labels reserve space for the sort icon even when the column isn't the active sort. This prevents layout changes when clicking on a column for sorting, but this also uses horizontal space. I think the icon should be hidden rather than of 0% opacity.
- [x] T... | Note that this is achievable in userland by passing a custom `classes` to the `<TableSortLabel>`:
```js
const styles = {
icon: {
display: 'none',
},
active: {
'& $icon': {
display: 'inline',
},
},
};
```
I just think it should be the default.
And anot... | 2018-09-14 16:39:42+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/TableSortLabel/TableSortLabel.test.js-><TableSortLabel /> has an icon when given direction asc should have asc direction class', 'packages/material-ui/src/TableSortLabel/TableSortLabel.test.js-><TableSortLabel /> prop: hideSortIcon does not hide icon by default when not active', 'packages/mat... | ['packages/material-ui/src/TableSortLabel/TableSortLabel.test.js-><TableSortLabel /> prop: hideSortIcon can hide icon when not active'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/TableSortLabel/TableSortLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/TableSortLabel/TableSortLabel.js->program->function_declaration:TableSortLabel"] |
mui/material-ui | 12,881 | mui__material-ui-12881 | ['12789'] | fc42dde03f4b78379b2d8ce32aa923ac283b32f4 | diff --git a/docs/src/pages/demos/chips/Chips.js b/docs/src/pages/demos/chips/Chips.js
--- a/docs/src/pages/demos/chips/Chips.js
+++ b/docs/src/pages/demos/chips/Chips.js
@@ -53,6 +53,13 @@ function Chips(props) {
onDelete={handleDelete}
className={classes.chip}
/>
+ <Chip
+ icon={<... | 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
@@ -501,4 +501,17 @@ describe('<Chip />', () => {
});
});
});
+
+ describe('prop: icon', () => {
+ it(... | [Chip] Support non-avatared icon on Chip
The Material Design spec allows us to put a simple icon which is not wrapped by an avatar component on Chips.
See https://material.io/design/components/chips.html#
But Chip of material-ui presupposes an Avatar as icon.
<!-- Checked checkbox should look like this: [x] -->
-... | @oliviertassinari @hidai I'd like to tackle this issue. I'm thinking it'd be better to use an "icon" attribute as opposed to extending the avatar attribute. That's more explicit and I imagine a little easier to code, easier to deal with from a testing standpoint and also a little more modular. What do you think?
@aret... | 2018-09-16 15:32:18+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> text only ... | ['packages/material-ui/src/Chip/Chip.test.js-><Chip /> prop: icon should render the icon'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Chip/Chip.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 5 | 1 | 6 | false | false | ["docs/src/pages/demos/chips/OutlinedChips.js->program->function_declaration:OutlinedChips", "docs/src/pages/demos/chips/ChipsPlayground.js->program->class_declaration:ChipsPlayground", "docs/src/pages/demos/chips/ChipsPlayground.js->program->class_declaration:ChipsPlayground->method_definition:render", "docs/src/pages... |
mui/material-ui | 12,968 | mui__material-ui-12968 | ['12965'] | ea462822d9881478efcf08829a60e3ff818f5d2d | diff --git a/docs/src/pages/demos/text-fields/ComposedTextField.js b/docs/src/pages/demos/text-fields/ComposedTextField.js
--- a/docs/src/pages/demos/text-fields/ComposedTextField.js
+++ b/docs/src/pages/demos/text-fields/ComposedTextField.js
@@ -1,10 +1,13 @@
import React from 'react';
+import ReactDOM from 'react-do... | diff --git a/packages/material-ui/src/OutlinedInput/NotchedOutline.test.js b/packages/material-ui/src/OutlinedInput/NotchedOutline.test.js
--- a/packages/material-ui/src/OutlinedInput/NotchedOutline.test.js
+++ b/packages/material-ui/src/OutlinedInput/NotchedOutline.test.js
@@ -48,7 +48,7 @@ describe('<NotchedOutline /... | Demo do not explain that FilledInput and OutlinedInput are needed instead of Input when you want Filled/Outlined textfields
- [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 ... | There is a `FilledInput` and `OutlinedInput` for this use case. We should update the demos in the documentation. | 2018-09-23 09:41:32+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/OutlinedInput/NotchedOutline.test.js-><NotchedOutline /> should be a fieldset', 'packages/material-ui/src/OutlinedInput/NotchedOutline.test.js-><NotchedOutline /> should pass props'] | ['packages/material-ui/src/OutlinedInput/NotchedOutline.test.js-><NotchedOutline /> should set alignment rtl'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/OutlinedInput/NotchedOutline.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 4 | 1 | 5 | false | false | ["packages/material-ui/src/TextField/TextField.js->program->class_declaration:TextField->method_definition:render", "docs/src/pages/demos/text-fields/ComposedTextField.js->program->class_declaration:ComposedTextField->method_definition:render", "packages/material-ui/src/OutlinedInput/NotchedOutline.js->program->functio... |
mui/material-ui | 12,969 | mui__material-ui-12969 | ['12949'] | d0ab3500dc9f88c3c31469e4e37fd663c3780fb6 | diff --git a/packages/material-ui/src/Drawer/Drawer.js b/packages/material-ui/src/Drawer/Drawer.js
--- a/packages/material-ui/src/Drawer/Drawer.js
+++ b/packages/material-ui/src/Drawer/Drawer.js
@@ -112,6 +112,7 @@ class Drawer extends React.Component {
render() {
const {
anchor: anchorProp,
+ Backd... | 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
@@ -487,4 +487,32 @@ describe('<S... | SwipeableDrawer needs `disableBackdropTransition` even with `hideBackdrop` or `BackdropProps.invisible`
<!--- 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... | @mikew Thank you for opening this issue, it's a great feedback!
- The `hideBackdrop` issue can be fixed with:
```diff
- if (!this.props.disableBackdropTransition) {
+ if (!this.props.disableBackdropTransition && !this.props.hideBackdrop) {
const backdropStyle = this.backdrop.style;
```
- The `Backd... | 2018-09-23 10:05:41+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> no backdrop does not crash when backdrop is hidden while swiping', 'packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> no backdrop does not crash when backdrop props are empty while swiping'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 3 | 1 | 4 | false | false | ["packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer->method_definition:getMaxTranslate", "packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer", "packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program-... |
mui/material-ui | 13,003 | mui__material-ui-13003 | ['12987'] | eb037957756f2d24b35d03906ac8e052d5138bc2 | diff --git a/packages/material-ui/src/StepLabel/StepLabel.d.ts b/packages/material-ui/src/StepLabel/StepLabel.d.ts
--- a/packages/material-ui/src/StepLabel/StepLabel.d.ts
+++ b/packages/material-ui/src/StepLabel/StepLabel.d.ts
@@ -16,6 +16,7 @@ export interface StepLabelProps
last?: boolean;
optional?: React.Reac... | diff --git a/packages/material-ui/src/StepLabel/StepLabel.test.js b/packages/material-ui/src/StepLabel/StepLabel.test.js
--- a/packages/material-ui/src/StepLabel/StepLabel.test.js
+++ b/packages/material-ui/src/StepLabel/StepLabel.test.js
@@ -59,6 +59,42 @@ describe('<StepLabel />', () => {
});
});
+ describ... | [StepIcon] Pass classes to icon component instead of simply render it.
That would be nice to provide StepIcon classes to the rendered icon when using custom icons.
It would allow to render the icon based on Step state.
<!-- Checked checkbox should look like this: [x] -->
- [x] This is not a v0.x issue. <!-- (v0.x ... | We could be adding a `StepIconComponent` property to the `StepLabel` component. This property would allow people to override this one:
https://github.com/mui-org/material-ui/blob/19c818842dba8208b1296173a8c7a7ddc6629c31/packages/material-ui/src/StepLabel/StepLabel.js#L105
@semos Do you want to work on it?
@oliviert... | 2018-09-25 21:07:08+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/StepLabel/StepLabel.test.js-><StepLabel /> prop: classes should set iconContainer', 'packages/material-ui/src/StepLabel/StepLabel.test.js-><StepLabel /> prop: completed renders <StepIcon> with the prop completed set to true', 'packages/material-ui/src/StepLabel/StepLabel.test.js-><StepLabel /... | ['packages/material-ui/src/StepLabel/StepLabel.test.js-><StepLabel /> prop: StepIconComponent should render'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/StepLabel/StepLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/StepLabel/StepLabel.js->program->function_declaration:StepLabel"] |
mui/material-ui | 13,067 | mui__material-ui-13067 | ['13063'] | 2be2826c70ba30762c8096a3e0971e334eb049fc | diff --git a/packages/material-ui/src/ListItemIcon/ListItemIcon.d.ts b/packages/material-ui/src/ListItemIcon/ListItemIcon.d.ts
--- a/packages/material-ui/src/ListItemIcon/ListItemIcon.d.ts
+++ b/packages/material-ui/src/ListItemIcon/ListItemIcon.d.ts
@@ -1,6 +1,7 @@
import { StandardProps } from '..';
-export interf... | diff --git a/packages/material-ui/src/ListItemIcon/ListItemIcon.test.js b/packages/material-ui/src/ListItemIcon/ListItemIcon.test.js
--- a/packages/material-ui/src/ListItemIcon/ListItemIcon.test.js
+++ b/packages/material-ui/src/ListItemIcon/ListItemIcon.test.js
@@ -16,23 +16,25 @@ describe('<ListItemIcon />', () => {
... | Allow color prop to override icon color when inside ListItemIcon
<!--- Provide a general summary of the feature in the Title above -->
Material design allows for list items to be colored with theme colors (as demonstrated [here](https://material.io/design/components/lists.html#types) under the "Expand and Collapse" he... | @izyb The simplest way to solve this problem is by using an intermediary component in the `ListItemIcon` implementation. I like the idea of removing a `React.cloneElement(` call.
@eps1lon What do you think?
Do you have a reproduction? It works on my end™: https://codesandbox.io/s/vmwx51nm07
@oliviertassinari
Look... | 2018-10-02 01:54:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | [] | ['packages/material-ui/src/ListItemIcon/ListItemIcon.test.js-><ListItemIcon /> should render a div with the user and root classes, but not the children classes', 'packages/material-ui/src/ListItemIcon/ListItemIcon.test.js-><ListItemIcon /> should render a span inside a div'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ListItemIcon/ListItemIcon.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/ListItemIcon/ListItemIcon.js->program->function_declaration:ListItemIcon"] |
mui/material-ui | 13,082 | mui__material-ui-13082 | ['12710'] | d3e2907f337fc9098b30a0ed05bca9f71983dc6a | diff --git a/docs/src/pages/demos/cards/ImgMediaCard.js b/docs/src/pages/demos/cards/ImgMediaCard.js
--- a/docs/src/pages/demos/cards/ImgMediaCard.js
+++ b/docs/src/pages/demos/cards/ImgMediaCard.js
@@ -14,7 +14,7 @@ const styles = {
maxWidth: 345,
},
media: {
- // ⚠️ object-fit is not supported by IE11.
... | 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
@@ -155,7 +155,7 ... | Drawer with keepMounted has incorrect aria-hidden value
<!--- Provide a general summary of the issue in the Title above -->
When using the following snippet:
```jsx
<Drawer
variant="temporary"
ModalProps={{
keepMounted: true
}}
{..other}
/>
```
The `aria-hidden` attribute logic ge... | null | 2018-10-03 04:52:53+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> mount should be able to access the native textarea', 'packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: onClickAway should not be call when clicking inside', 'packages/material-ui/src/ClickAwayListener/... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: keepMounted should mount', 'packages/material-ui/src/Modal/ModalManager.test.js->ModalManager container aria-hidden should not contain aria-hidden on modal', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleDocumentKeyDown() when mounted, Top... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js packages/material-ui/src/Modal/Modal.test.js packages/material-ui/src/Modal/ModalManager.test.js packages/material-ui/src/InputBase/InputBase.test.js packages/material-ui... | Bug Fix | false | false | false | true | 11 | 3 | 14 | false | false | ["packages/material-ui/src/InputBase/InputBase.js->program->class_declaration:InputBase", "packages/material-ui/src/Modal/manageAriaHidden.js->program->function_declaration:ariaHidden", "packages/material-ui/src/Modal/Modal.js->program->class_declaration:Modal->method_definition:componentDidUpdate", "packages/material-... |
mui/material-ui | 13,091 | mui__material-ui-13091 | ['13070'] | 770c375ad020884b0eeda376302ef40f42b09657 | 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
@@ -147,6 +147,9 @@ class SelectInput extends React.Component {
node: ref,
// By pass the n... | 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
@@ -354,5 +354,19 @@ describe('<SelectInput />', () => {
mount(<SelectInput {.... | [TextField] "Uncaught TypeError: r.inputRef.focus is not a function" when clicking on InputAdornment
<!--- Provide a general summary of the issue in the Title above -->
Uncaught TypeError: r.inputRef.focus is not a function when clicking on InputAdornment
please take a look on screenshot below
<!--
Thank you ve... | This is caused by https://github.com/mui-org/material-ui/blob/e30c2ac7e2d2ff52e6dc7a63e0bcf1199fe4329d/packages/material-ui/src/Select/SelectInput.js#L146-L152
Not sure why this is used. I guess this is for internal usage only? Any insight @oliviertassinari
A diff like this should do it:
```diff
const nodeProx... | 2018-10-03 14:26:20+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: displayEmpty should display the selected item even if its value is empty', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: MenuProps should be able to override PaperProps minWidth', 'packages/material-ui/src/Select/... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: inputRef should be able to return the input focus proxy function', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: inputRef should be able to hit proxy function'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput"] |
mui/material-ui | 13,138 | mui__material-ui-13138 | ['12302'] | 965776002fcf482b65d66040393cf75caa18d356 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of all the material-ui modules.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '93.1 KB',
+ limit: '93.2 KB',
},
{
name: 'Th... | 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
@@ -233,4 +233,13 @@ describe('<Tooltip />', () => {
);
});
});
+
+ it('should fo... | Tooltip inside CardActions raises Warning: Failed prop type
<!--- Provide a general summary of the issue in the Title above -->
Titled case raises Warning: Failed prop type: The following properties are not supported: `className`. Please remove them. The issue started to appear after recent reimplementation of `Toolti... | I'm experiencing the same issue inside of a FormGroup.
I've been experiencing the same issue inside a ListItemIcon.
Wrap your Tooltip inside a React.Fragment and the warning doesn't show up anymore.
```javascript
<ListItem>
<ListItemIcon>
<React.Fragment>
<Tooltip placement="top" title="Hello !">
... | 2018-10-07 18:10:13+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> should forward properties to the child element'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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->class_declaration:Tooltip->method_definition:render"] |
mui/material-ui | 13,188 | mui__material-ui-13188 | ['13147'] | f11ae6663cb51a100beb812516ef8eafbbc0c1ce | diff --git a/packages/material-ui/src/Stepper/Stepper.js b/packages/material-ui/src/Stepper/Stepper.js
--- a/packages/material-ui/src/Stepper/Stepper.js
+++ b/packages/material-ui/src/Stepper/Stepper.js
@@ -84,7 +84,7 @@ function Stepper(props) {
key: index, // eslint-disable-line react/no-array-index-key
... | diff --git a/packages/material-ui/src/Stepper/Stepper.test.js b/packages/material-ui/src/Stepper/Stepper.test.js
--- a/packages/material-ui/src/Stepper/Stepper.test.js
+++ b/packages/material-ui/src/Stepper/Stepper.test.js
@@ -199,4 +199,17 @@ describe('<Stepper />', () => {
);
assert.strictEqual(wrapper.find... | Multiple active steps not working
<!--- 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: ... | I think setting `active` on all Steps is a hacky way to achieve what #12948 is asking for. The change was caused by #13023.
The fix is pretty simple. Changing the order in https://github.com/spirosikmd/material-ui/blob/89f6c30fbf38e0ce87cd6bb5554bd460ef343e25/packages/material-ui/src/Stepper/Stepper.js#L88
should b... | 2018-10-10 16:44:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Stepper/Stepper.test.js-><Stepper /> step connector should pass completed prop to connector when second step is completed', 'packages/material-ui/src/Stepper/Stepper.test.js-><Stepper /> renders with a null child', 'packages/material-ui/src/Stepper/Stepper.test.js-><Stepper /> controlling chi... | ['packages/material-ui/src/Stepper/Stepper.test.js-><Stepper /> should be able to force a state'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Stepper/Stepper.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Stepper/Stepper.js->program->function_declaration:Stepper"] |
mui/material-ui | 13,233 | mui__material-ui-13233 | ['4305'] | 77da64923b9fbe7798a06d14c337504c9a962d68 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of all the material-ui modules.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '92.7 KB',
+ limit: '93.2 KB',
},
{
name: 'Th... | 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
@@ -633,7 +633,10 @@ describe('<ButtonBase />', () => {
wrapper.se... | [Discussion] Benchmark components
I've done a benchmark page between `material-ui` and `react-toolbox` because I wanted evaluated the alternatives that might have better performance. I will be happy if you guys could do some PRs with more benchmarks. I think you can get some benefit by doing this because you can see wh... | @EloB We're working on big performance improvements for `0.16.0`. We're tackling styles first as that is a global perf issue, and then going to look component-by-component at specifics caused by other issues.
It's unlikely that we're going to want to make a big song and dance about benchmark results until the big know... | 2018-10-13 21:41:06+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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/styles/MuiThemeProvider.test.js-><MuiThemeProvider /> server side should be able to extract the styles'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha test/utils/setup.js packages/material-ui/src/ButtonBase/ButtonBase.test.js packages/material-ui/src/styles/MuiThemeProvider.test.js test/utils/rerender.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 4 | 0 | 4 | false | false | ["packages/material-ui/src/ButtonBase/createRippleHandler.js->program->function_declaration:createRippleHandler", "packages/material-ui/src/NoSsr/NoSsr.js->program->class_declaration:NoSsr->method_definition:componentDidMount", "packages/material-ui/src/Button/Button.js->program->function_declaration:Button", "packages... |
mui/material-ui | 13,320 | mui__material-ui-13320 | ['12819'] | 615318b7a93eed443e98bd34bc14a16897bf7e02 | 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
@@ -177,12 +177,24 @@ function getOffset(node) {
};
}
-function getMousePosition(event) {
- if (event.... | 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
@@ -4,6 +4,11 @@ import { assert } from 'chai';
import { createMount, createShallow, get... | [Slider] Not able for multi-touch, but native range slider is
With this example you can compare multi-touch behaviour of Material-UI Lab Sliders towards native range input sliders (you need to have a touch device availlable and at least two fingers)
PS: What I mean with range input slider is something like this:
... | null | 2018-10-21 09:37:29+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ["packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> prop: disabled should not call 'onChange' handler", 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> when mouse leaves window should move to the end', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> should render with the de... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> should only listen to changes from the same touchpoint'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | false | false | true | 4 | 1 | 5 | false | false | ["packages/material-ui-lab/src/Slider/Slider.js->program->function_declaration:getMousePosition", "packages/material-ui-lab/src/Slider/Slider.js->program->function_declaration:calculatePercent", "packages/material-ui-lab/src/Slider/Slider.js->program->class_declaration:Slider", "packages/material-ui-lab/src/Slider/Slid... |
mui/material-ui | 13,389 | mui__material-ui-13389 | ['13365'] | 7f6eda023d8677a1147b38d58551b9b2ee7aa615 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of all the material-ui modules.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '93.0 KB',
+ limit: '93.1 KB',
},
{
name: 'Th... | 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
@@ -163,16 +163,16 @@ describe('<Menu />', () => {
});
it('should call props.onEnter with element if exists',... | Still having trouble with Modals and removeAttribute in 3.3.1
See issue #13349 and others referenced.
I have a menu with several items. Clicking on a menu item is supposed to open another modal but it crashes the whole React DOM with the error ```Uncaught TypeError: Cannot read property 'removeAttribute' of undefine... | still +1, in version @3.1.1 When right/top menu with items trigger OnClick, page crashed along with error message. `Uncaught TypeError: Cannot read property 'removeAttribute' of undefined.` 😢
Thx for the timely hotfix @3.3.1.
How can we reproduce it?
it happen on mine too
confirmed 3.1.1 still have the same beh... | 2018-10-25 22:59:39+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Menu/Menu.test.js-><Menu /> mount menuList.selectedItemRef exists should not set style on list when element.clientHeight == list.clientHeight', '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... | ['packages/material-ui/test/integration/NestedMenu.test.js-><NestedMenu> integration mounted open should focus the first item of second menu', 'packages/material-ui/test/integration/NestedMenu.test.js-><NestedMenu> integration mounted open should be able to open second menu again', 'packages/material-ui/src/Menu/Menu.t... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/NestedMenu.test.js packages/material-ui/src/Menu/Menu.test.js packages/material-ui/test/integration/fixtures/menus/NestedMenu.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 3 | 2 | 5 | false | false | ["packages/material-ui/src/Modal/Modal.js->program->class_declaration:Modal->method_definition:componentDidUpdate", "packages/material-ui/src/Modal/ModalManager.js->program->class_declaration:ModalManager->method_definition:remove", "packages/material-ui/src/Modal/Modal.js->program->class_declaration:Modal", "packages/... |
mui/material-ui | 13,408 | mui__material-ui-13408 | ['12047'] | fa2b154ffb5daaf0dce0da22931f36802c03391b | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,13 +22,13 @@ module.exports = [
name: 'The size of all the material-ui modules.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '93.2 KB',
+ limit: '93.3 KB',
},
{
name: '... | 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
@@ -61,6 +61,39 @@ describe('<SelectInput />', () => {
);
});
+ describe('... | [SelectInput] Allow selected to be chosen with non-strict equality
## Problem (short story)
Detection of the selected choice in `SelectInput` uses strict equality (`===`) with no option for a non-strict equality fallback. This prevents value initialization from the query string (which isn't strongly typed).
## Co... | @fzaninotto Interesting issue. Of course, you can always normalize the data on React Admin side. Still, I'm eager to see how the native implementation behaves. I think that we should make them (native, non-native) identical. I'm gonna try/test that and see how we can move forward.
All green for me, it does work this w... | 2018-10-27 10:28:59+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: autoWidth should take the anchor width into account', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: readOnly should not trigger any event with readOnly', 'packages/material-ui/src/Select/SelectInput.test.js-><Sele... | ['packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: value should select only the option that matches the object', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: multiple when the value matches an option but they are different types should select the options based on... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput->method_definition:render", "packages/material-ui/src/Select/SelectInput.js->program->function_declaration:areEqualValues"] |
mui/material-ui | 13,409 | mui__material-ui-13409 | ['12420'] | ad8695b5771b2f6bec66f0b20b409425cf8e629d | diff --git a/BACKERS.md b/BACKERS.md
--- a/BACKERS.md
+++ b/BACKERS.md
@@ -68,7 +68,7 @@ via [Patreon](https://www.patreon.com/oliviertassinari)
| Avétis KAZARIAN | Withinpixels | SIM KIM SIA | Renaud Bompuis | Yaron Malin |
| Arvanitis Panagiotis | Jesse Weigel | Bogdan Mihai Nicolae | Dung Tran | Kyle Pennell |
| ... | 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
@@ -277,7 +277,7 @@ describe('<SpeedDial />', () => {
it('... | Unable to interact with scrollbar when Dialog scroll='body'
<!--- Provide a general summary of the issue in the Title above -->
When using a Dialog with scroll='body', the only way to scroll is to use the Page Up/Down or Up/Down keys. Clicking or dragging the scrollbar causes the dialog to close.
<!--
Thank y... | Note: using `disableBackdropClick` does not work either :/
Another problem with using "scroll=body" is that you'll get scrollbar flickering when animating the dialog using an transition (eg. slideup) | 2018-10-27 12:24:16+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> positioning on an anchor should pass through container prop if container and anchorEl props are provided', 'packages/material-ui-lab/src/SpeedDi... | ['packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> backdrop should ignore the backdrop click if the event did not come from the backdrop', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> backdrop should call through to the user specified onBackdropClick callback', 'packages/material-ui/src/Dialog/... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/DialogTitle/DialogTitle.test.js packages/material-ui/src/DialogContent/DialogContent.test.js packages/material-ui/src/Card/Card.test.js packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js packages/material-ui/... | Bug Fix | false | false | false | true | 3 | 1 | 4 | false | false | ["packages/material-ui/src/Dialog/Dialog.js->program->function_declaration:Dialog", "packages/material-ui/src/Dialog/Dialog.js->program->class_declaration:Dialog->method_definition:render", "packages/material-ui/src/Dialog/Dialog.js->program->class_declaration:Dialog", "docs/src/modules/components/Ad.js->program->funct... |
mui/material-ui | 13,430 | mui__material-ui-13430 | ['10327'] | fa2b154ffb5daaf0dce0da22931f36802c03391b | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -28,7 +28,7 @@ module.exports = [
name: 'The main docs bundle',
webpack: false,
path: main.path,
- limit: '182 KB',
+ limit: '183 KB',
},
{
name: 'The docs home page',
diff --git a/docs/src/pages/de... | diff --git a/packages/material-ui/src/CircularProgress/CircularProgress.test.js b/packages/material-ui/src/CircularProgress/CircularProgress.test.js
--- a/packages/material-ui/src/CircularProgress/CircularProgress.test.js
+++ b/packages/material-ui/src/CircularProgress/CircularProgress.test.js
@@ -105,9 +105,38 @@ desc... | CircularProgress, length of the line does not animate under load
<!-- Checked checkbox should look like this: [x] -->
- [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
CircularProgress animation should... | The circular progress animation requires CPU/GPU processing power to run, much more than a simple rotation. I don't think that we could do anything to improve the current situation. It's definitely a limitation. Under heavy load, we lose the stroke dash animation, the only thing that keeps working is the rotation. At l... | 2018-10-28 22:03:54+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/CircularProgress/CircularProgress.test.js-><CircularProgress /> should render a div with the root class', 'packages/material-ui/src/CircularProgress/CircularProgress.test.js-><CircularProgress /> should contain an SVG with the svg class, and a circle with the circle class', 'packages/material... | ['packages/material-ui/src/CircularProgress/CircularProgress.test.js-><CircularProgress /> prop: disableShrink should render with disableShrink class when set to true'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/CircularProgress/CircularProgress.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 6 | 0 | 6 | false | false | ["docs/src/pages/demos/progress/LinearIndeterminate.js->program->function_declaration:LinearIndeterminate", "docs/src/pages/demos/progress/CircularDeterminate.js->program->class_declaration:CircularDeterminate->method_definition:render", "pages/demos/progress.js->program->function_declaration:Page", "pages/getting-star... |
mui/material-ui | 13,452 | mui__material-ui-13452 | ['13438', '13438'] | 653138606fbe9538082507615ae20af55746e188 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -16,13 +16,13 @@ module.exports = [
name: 'The initial cost paid for using one component',
webpack: true,
path: 'packages/material-ui/build/Paper/index.js',
- limit: '17.8 KB',
+ limit: '17.9 KB',
},
{
... | 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
@@ -22,6 +22,12 @@ describe('createMuiTheme', () => {
assert.notStri... | createMuiTheme uses default spacing for createMixins instead of overrides
<!--- 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.
-->
<!-- ... | @zsalzbank Yes, you are right, we should be using the spacing value people are providing in
https://github.com/mui-org/material-ui/blob/fa2b154ffb5daaf0dce0da22931f36802c03391b/packages/material-ui/src/styles/createMuiTheme.js#L15-L22
A change like this + a unit test should do it:
```diff
--- a/packages/material-... | 2018-10-30 16:29:59+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 should use the defined spacing unit for the gutters mixin'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 13,483 | mui__material-ui-13483 | ['13447'] | 979346a189289a47abc7f08df94d2e7d01141ca2 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of all the material-ui modules.',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.0 KB',
+ limit: '94.1 KB',
},
{
name: 'Th... | 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
@@ -263,6 +263,65 @@ describe('<ButtonBase />', () => {
});
});
... | [ButtonBase] Shadow Root activeElement resolution
When using custom elements with a shadowRoot, the `focusVisibleClassName` is applied to the outer-most custom element, instead of the actual element that is focused within the shadow DOM.
## Expected Behavior
`focusVisibleClassName` should be added to deepest-level ... | Does `:focus-visible` also apply to elements within a shadow root?
> Does `:focus-visible` also apply to elements within a shadow root?
This is potentially handled by `delegatesFocus`? http://w3c.github.io/webcomponents/spec/shadow/#widl-ShadowRootInit-delegatesFocus
Although, a similar issue to this one was rais... | 2018-11-01 13:57:58+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> focus inside shadowRoot should set focus state for shadowRoot children'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 2 | 0 | 2 | false | false | ["packages/material-ui/src/ButtonBase/focusVisible.js->program->function_declaration:findActiveElement", "packages/material-ui/src/ButtonBase/focusVisible.js->program->function_declaration:detectFocusVisible"] |
mui/material-ui | 13,494 | mui__material-ui-13494 | ['13488'] | 43e43e7839a032802d31a4df83c8ba5afc8fb49d | diff --git a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js
--- a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js
+++ b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js
@@ -138,7 +138,6 @@ T... | diff --git a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js
--- a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js
+++ b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js
@... | [ToggleButtonGroup] Falsy values cause the background/shadow to disappear
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] This is a Labs issue.
- [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.
... | https://github.com/mui-org/material-ui/blob/979346a189289a47abc7f08df94d2e7d01141ca2/packages/material-ui-lab/src/ToggleButtonGroup/hasValue.js#L7
vs.
https://github.com/mui-org/material-ui/blob/979346a189289a47abc7f08df94d2e7d01141ca2/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js#L52
`hasVal... | 2018-11-02 16:39:30+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui-lab/src/ToggleButtonGroup/hasValue.test.js-><ToggleButton /> hasValue should be false for undefined', 'packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js-><ToggleButtonGroup /> prop: onChange exclusive should be a single value when value is toggled on', 'packages/material-ui... | ['packages/material-ui-lab/src/ToggleButtonGroup/hasValue.test.js-><ToggleButton /> hasValue should be true for empty string'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/ToggleButtonGroup/hasValue.test.js packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/ToggleButtonGroup/hasValue.js->program->function_declaration:hasValue"] |
mui/material-ui | 13,499 | mui__material-ui-13499 | ['12063'] | 5ed754d2144807378ec94af80cb22b9fe9a51388 | diff --git a/docs/src/pages/demos/selection-controls/FormControlLabelPosition.js b/docs/src/pages/demos/selection-controls/FormControlLabelPosition.js
new file mode 100644
--- /dev/null
+++ b/docs/src/pages/demos/selection-controls/FormControlLabelPosition.js
@@ -0,0 +1,58 @@
+import React from 'react';
+import Radio f... | diff --git a/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js b/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js
--- a/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js
+++ b/packages/material-ui/src/FormControlLabel/FormControlLabel.test.js
@@ -56,12 +56,26 @@ descr... | [FormControlLabel] Add labelPlacement?: 'top' | 'bottom'
Currently the FormControlLabel only allows the label to appear on the right of the Control (Switch, Radio, Checkbox). It would be helpful to provide a property to position the Label on the Top, Right and Left.
| I'm closing as a duplicate of #11618
@oliviertassinari I don't think it's really a duplicate. I'm looking to add a label top on a Checkbox, and it seems not possible.
ex:
@JulienMalige Sure, we can add th... | 2018-11-03 12:35:27+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> with muiFormControl context disabled should have the disabled class', 'packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: disabled should disable everything 1', 'packages/material-ui/sr... | ['packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: labelPlacement should have the `bottom` class', 'packages/material-ui/src/FormControlLabel/FormControlLabel.test.js-><FormControlLabel /> prop: labelPlacement should have the `top` class'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/FormControlLabel/FormControlLabel.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/FormControlLabel/FormControlLabel.js->program->function_declaration:FormControlLabel", "pages/demos/selection-controls.js->program->function_declaration:Page"] |
mui/material-ui | 13,534 | mui__material-ui-13534 | ['10466'] | 20cd3e33ae60e4970653716b7732212e93bab38c | diff --git a/docs/src/pages/demos/badges/BadgeVisibility.js b/docs/src/pages/demos/badges/BadgeVisibility.js
new file mode 100644
--- /dev/null
+++ b/docs/src/pages/demos/badges/BadgeVisibility.js
@@ -0,0 +1,58 @@
+import React, { Component } from 'react';
+import PropTypes from 'prop-types';
+import { withStyles } fro... | 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
@@ -118,4 +118,49 @@ describe('<Badge />', () => {
assert.strictEqual(wrapper.contains(testChildren), true);... | [Badge] Add disabled property to quick hide/show
<!--- 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... | @djeeg You can use the `classes.badge` CSS API to change the style as you see fit. For instance, you could add `display: none`/`visibility: hidden`.
> Dont really want to end up like this
> Could inject different styles, a bit messy
@djeeg Yes, these are two valide alternatives. You can build an abstraction on top ... | 2018-11-06 23:01:56+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Badge/Badge.test.js-><Badge /> renders children and have primary styles', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> have error class', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> renders children and have secondary styles', 'packages/material-ui/src/Badge/Badge.tes... | ['packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: invisible should render with the invisible class when set to true'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Badge/Badge.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Badge/Badge.js->program->function_declaration:Badge", "pages/demos/badges.js->program->function_declaration:Page"] |
mui/material-ui | 13,582 | mui__material-ui-13582 | ['13577'] | a2c35232889603e3f2c5930403a4df1a90a37ece | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.1 KB',
+ limit: '94.2 KB',
},
{
name: 'T... | diff --git a/packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js b/packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js
--- a/packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js
+++ b/packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelS... | [Accordion] onBlur event for Summary doesn't fire
<!--- 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 ... | @crpc Well spotted! It's definitely a bug. We are overriding the user's onBlur property:
https://github.com/mui-org/material-ui/blob/83adb95e594d7799b5f399a824f0d72f749ba349/packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.js#L130-L132
without calling it when needed:
https://github.com/mui-org/m... | 2018-11-13 03:46:03+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js-><ExpansionPanelSummary /> when expanded should have expanded class', 'packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js-><ExpansionPanelSummary /> handleBlur() should unset focused state', 'packages/material-ui/sr... | ['packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js-><ExpansionPanelSummary /> handleFocusVisible() should set focused state', 'packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js-><ExpansionPanelSummary /> event callbacks should fire event callbacks'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.js->program->class_declaration:ExpansionPanelSummary->method_definition:render", "packages/material-ui/src/ExpansionPanelSummary/ExpansionPanelSummary.js->program->class_declaration:ExpansionPanelSummary"] |
mui/material-ui | 13,661 | mui__material-ui-13661 | ['10845'] | 086a6a55bbab7b5ae079088f4cf37163eb3ed961 | diff --git a/packages/material-ui/src/Input/Input.js b/packages/material-ui/src/Input/Input.js
--- a/packages/material-ui/src/Input/Input.js
+++ b/packages/material-ui/src/Input/Input.js
@@ -133,7 +133,15 @@ Input.propTypes = {
/**
* The default input value, useful when not controlling the component.
*/
- d... | 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
@@ -85,4 +85,21 @@ describe('<Select />', () => {
assert.strictEqual(React.isValidElement(selected... | Support objects with <Select>
<!--- 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] ... | @npeham Do you have a full reproduction example? It's hard to tell what's wrong without. You could be using CodeSandbox or StackBlitz.
Did you know if you have installed the material types? npm uninstall @types/material-ui work for me!
@oliviertassinari Sure: https://codesandbox.io/s/8x8r5plx32?module=%2Fsrc%2Fpages%... | 2018-11-21 10:22:04+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Select/Select.test.js-><Select /> should provide the classes to the input component', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: onChange should get selected element from arguments', 'packages/material-ui/src/Select/Select.test.js-><Select /> prop: inputProps should be ... | ['packages/material-ui/src/Select/Select.test.js-><Select /> prop: value should be able to use an object'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 13,686 | mui__material-ui-13686 | ['13680'] | ddfa8e0215bfe895efcb8da69f1ea3cc3b1370ff | diff --git a/docs/src/modules/components/Demo.js b/docs/src/modules/components/Demo.js
--- a/docs/src/modules/components/Demo.js
+++ b/docs/src/modules/components/Demo.js
@@ -36,7 +36,7 @@ function getDemo(props) {
return {
title: 'Material demo',
description: props.githubLocation,
- dependencies: getDe... | 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
@@ -33,7 +33,7 @@ import { withStyles } from '@material-ui/core/styles';
const suggestions = [`;
describe('docs getDependencies helpe... | [docs] makeStyles demo is broken
<!--- 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: [... | > Demo needs to be updated to use react 16.7.0 alpha
@joshwooding Run warn and you should be good: https://github.com/mui-org/material-ui/blob/46cb140174ae40c4751cb49326157dc7fc499955/package.json#L131
@oliviertassinari https://codesandbox.io/s/0mpw102k00 I meant this demo. The docs demo works fine but the edit in c... | 2018-11-24 21:36:23+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | [] | ['docs/src/modules/utils/helpers.test.js->docs getDependencies helpers generates the right npm dependencies'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 2 | 0 | 2 | false | false | ["docs/src/modules/utils/helpers.js->program->function_declaration:getDependencies", "docs/src/modules/components/Demo.js->program->function_declaration:getDemo"] |
mui/material-ui | 13,689 | mui__material-ui-13689 | ['13681'] | f78ac878770683b6b8937d82b164b946d9c0a5ee | 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
@@ -13,6 +13,8 @@ import ownerDocumen... | 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
@@ -5,6 +5,16 @@ ... | ClickAwayListener to ignore touchmove events
<!-- 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.
##... | @hsimah Thank you for opening this issue. I agree it's an important concern, we should be taking care of it. You need the state in your workaround, it can be a class instance variable. Otherwise, we can use a similar logic internally 👍. Do you want to work on it? :) | 2018-11-24 23:20:53+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> swipe to open anchor=left should let user scroll the page', 'packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: onClickAway should not be call when clicking inside', 'packages/material-... | ['packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js-><ClickAwayListener /> prop: touchEvent should ignore `touchend` when preceeded by `touchmove` event'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ClickAwayListener/ClickAwayListener.test.js packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/ClickAwayListener/ClickAwayListener.js->program->class_declaration:ClickAwayListener", "packages/material-ui/src/ClickAwayListener/ClickAwayListener.js->program->class_declaration:ClickAwayListener->method_definition:render"] |
mui/material-ui | 13,690 | mui__material-ui-13690 | ['13346'] | ce642582728c63d1837e0a3e3fd455be4b260950 | 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
@@ -278,9 +278,15 @@ class Tooltip extends React.Component {
open = false;
}
+ // For accessibility ... | 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
@@ -44,8 +44,21 @@ describe('<Tooltip />', () => {
assert.strictEqual(wrapper.childAt(1).has... | [Tooltip] disableHoverListener shows title
The uncontrolled tooltip with disableHoverListener set on true.
## Expected Behavior
The setup disableHoverListener property affects the visibility of the standard html title property
## Current Behavior
When the disableHoverListener prop is true and open prop is... | Isn't that what it's supposed to do? Don't prevent the default behavior and fallback to native tooltip behavior?
What is to use case for this? Why would you use the Tooltip component if you never want to display a tooltip?
I guess you issue is that you're passing `undefined` to `open` while you consider that Tool... | 2018-11-25 01:08:48+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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: disableHoverListener should hide the native title'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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->class_declaration:Tooltip->method_definition:render"] |
mui/material-ui | 13,719 | mui__material-ui-13719 | ['13717'] | 2ce70f048358680ef96536fd34c8ac679710bdca | diff --git a/packages/material-ui/src/FilledInput/FilledInput.d.ts b/packages/material-ui/src/FilledInput/FilledInput.d.ts
--- a/packages/material-ui/src/FilledInput/FilledInput.d.ts
+++ b/packages/material-ui/src/FilledInput/FilledInput.d.ts
@@ -2,7 +2,9 @@ import * as React from 'react';
import { StandardProps, Prop... | diff --git a/packages/material-ui/src/FilledInput/FilledInput.test.js b/packages/material-ui/src/FilledInput/FilledInput.test.js
--- a/packages/material-ui/src/FilledInput/FilledInput.test.js
+++ b/packages/material-ui/src/FilledInput/FilledInput.test.js
@@ -1,18 +1,32 @@
import React from 'react';
import { assert } ... | Filled TextField doesn't respect disableUnderline input prop
- [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.
**I saw #13085 issue with same problem and... | Doesn't look like `FilledInput` is handling `disableUnderline` at all. Looks like we only need to apply conditional logic to the `underlined` from https://github.com/mui-org/material-ui/blob/1c8c88781c5d48915099cf4db17f255c17b052e5/packages/material-ui/src/Input/Input.js#L103 to here https://github.com/mui-org/material... | 2018-11-28 11:03:22+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent should inject onBlur and onFocus', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> mount should be able to access the native textarea', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> con... | ['packages/material-ui/src/FilledInput/FilledInput.test.js-><FilledInput /> should disable the underline'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/FilledInput/FilledInput.test.js packages/material-ui/src/InputBase/InputBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/material-ui/src/InputBase/InputBase.js->program->class_declaration:InputBase->method_definition:render", "packages/material-ui/src/FilledInput/FilledInput.js->program->function_declaration:FilledInput", "packages/material-ui/src/OutlinedInput/OutlinedInput.js->program->function_declaration:OutlinedInput"] |
mui/material-ui | 13,726 | mui__material-ui-13726 | ['13710'] | 53e44d50086c7d98231c477b1d3e98b82554dc0f | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.9 KB',
+ limit: '95 KB',
},
{
name: 'The... | diff --git a/packages/material-ui/src/internal/SwitchBase.test.js b/packages/material-ui/src/internal/SwitchBase.test.js
--- a/packages/material-ui/src/internal/SwitchBase.test.js
+++ b/packages/material-ui/src/internal/SwitchBase.test.js
@@ -7,6 +7,7 @@ import {
getClasses,
unwrap,
} from '@material-ui/core/tes... | [SwitchBase] Not throwing errors when uncontrolled input changes to a controlled one
<!--- 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.
-... | 😱
It's a regression introduced after #10444. We need a test.
Ok, I have figured it out. I propose the following path:
1. We add a regression test (if possible). It's important to have the React warning
2. We fix the implementation:
```diff
>
{checked ? checkedIcon : icon}
<input
... | 2018-11-29 00:04:32+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> should disable the components, and render the IconButton with the disabled className', 'packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> uncontrolled should uncheck the checkbox', 'packages/material-ui/src/internal/SwitchBase.tes... | ['packages/material-ui/src/internal/SwitchBase.test.js-><SwitchBase /> check transitioning between controlled states throws errors should error when uncontrolled and changed to controlled'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/internal/SwitchBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/internal/SwitchBase.js->program->class_declaration:SwitchBase->method_definition:render"] |
mui/material-ui | 13,743 | mui__material-ui-13743 | ['13733'] | d8a71892231d3fbfac42c2e2e8631591d25f825a | 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
@@ -124,7 +124,7 @@ class ModalManager {
const containerIdx = findIndexOf(this.data, item => item.mo... | 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,6 +1,7 @@
import React from 'react';
import { assert } from 'chai';
import { spy, stub } from 'sinon';
+... | [Dialog] Simultaneously closing multiple dialogs throws an error
- [x] This is not a v0.x issue.
- [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 🤔
Both dialog boxes should close, with no error.
#... | 
it throws here https://github.com/oliviertassinari/material-ui/blob/840738330c85c6d7a2f313432c21401082e687a4/packages/material-ui/src/Modal/ModalManager.js#L53
since `data.style` is `undefined`
and prob... | 2018-11-29 23:32:56+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should render a backdrop component into the portal before the modal content', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleDocumentKeyDown() should... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> two modal at the same time should open and close'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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->class_declaration:ModalManager->method_definition:mount"] |
mui/material-ui | 13,759 | mui__material-ui-13759 | ['13751'] | e690a395926624b540d90ee20fcadeda0070ff49 | diff --git a/packages/material-ui/src/Avatar/Avatar.js b/packages/material-ui/src/Avatar/Avatar.js
--- a/packages/material-ui/src/Avatar/Avatar.js
+++ b/packages/material-ui/src/Avatar/Avatar.js
@@ -20,7 +20,6 @@ export const styles = theme => ({
userSelect: 'none',
},
/* Styles applied to the root element i... | 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
@@ -134,4 +134,31 @@ describe('<Avatar />', () => {
assert.strictEqual(wrapper.hasClass(classes.co... | [Avatar] Avatar does not apply colorDefault class when child is 0
The Avatar component does not apply its colorDefault class when its children are a falsey value, including 0
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off th... | @camilleryr Thank you for opening this issue. It's definitely wrong. I would try to push that one step further:
```diff
const className = classNames(
classes.root,
{
- [classes.colorDefault]: childrenProp && !src && !srcSet,
+ [classes.colorDefault]: !src && !srcSet,
},
classNameProp,
... | 2018-11-30 22:36:52+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Avatar/Avatar.test.js-><Avatar /> svg icon avatar should apply the childrenClassName class', '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 ... | ['packages/material-ui/src/Avatar/Avatar.test.js-><Avatar /> falsey avatar should apply the colorDefault class'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Avatar/Avatar.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Avatar/Avatar.js->program->function_declaration:Avatar"] |
mui/material-ui | 13,778 | mui__material-ui-13778 | ['13777'] | 550e949bab55d3fe3f3aba04f76baa7e45d324cc | 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
@@ -50,9 +50,12 @@ function setContainerStyle(data) {
}
function removeContainerStyle(data) {
- Obje... | 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
@@ -541,4 +541,27 @@ describe('<Modal />', () => {
assert.strictEqual(document.body.style.overflow, '');
... | Cannot convert undefined or null to object
After a migration to the 3.6.1 version and when I open a Modal. I have the following error:
`data.style is undefined`
![error](https://user-images.githubus... | null | 2018-12-03 10:43:33+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleDocumentKeyDown() should have handleDocumentKeyDown', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleDocumentKeyDown() should not be call when defaultPrevented', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should attac... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> should support open abort', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: open should render the modal div inside the portal', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> render should render the content into the portal', 'packages/... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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:removeContainerStyle"] |
mui/material-ui | 13,789 | mui__material-ui-13789 | ['13648'] | 42c60e9848696ebc167d87e1743222e758d0213e | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '94.5 KB',
+ limit: '94.6 KB',
},
{
name: 'T... | 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
@@ -129,15 +129,11 @@ describe('<Dialog />', () => {
wrapper.setProps({ onClose });
const... | [Dialog] onBackdropClick event fires when draggable item released on it
If Dialog contains any draggable component (e.g. sortable list from [react-sortable-hoc](https://clauderic.github.io/react-sortable-hoc/)) and this component have been dragging and has released over 'backdrop zone' then onBackdropClick event fires.... | This happens for any MUI Dialog in chrome and is reproducible on the demo page: https://material-ui.com/demos/dialogs/.
Just mouse down on a dialog, move your mouse off and when you mouse up the Dialog will close
@oliviertassinari looking at bootstrap they seem to handle this using:
```
$(this._dialog).on(Event.MO... | 2018-12-04 00:39:42+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> should be open by default', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> prop: fullScreen false should not render fullScreen', '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 /> backdrop should store the click target on mousedown', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> backdrop should clear click target on successful backdrop click', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> backdrop should not... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Dialog/Dialog.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/Dialog/Dialog.js->program->class_declaration:Dialog->method_definition:render", "packages/material-ui/src/Dialog/Dialog.js->program->class_declaration:Dialog"] |
mui/material-ui | 13,797 | mui__material-ui-13797 | ['13792'] | 120eef02054bce6190b4d39837517d9ac41ef593 | diff --git a/packages/material-ui/src/Dialog/Dialog.js b/packages/material-ui/src/Dialog/Dialog.js
--- a/packages/material-ui/src/Dialog/Dialog.js
+++ b/packages/material-ui/src/Dialog/Dialog.js
@@ -10,6 +10,7 @@ import { capitalize } from '../utils/helpers';
import Modal from '../Modal';
import Fade from '../Fade';
... | 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
@@ -1,13 +1,15 @@
import React from 'react';
import { assert } from 'chai';
import { spy } from 'sinon... | [Dialog] Setting paper classname removes other classes
When providing custom `PaperProps` with a `className` to a `Modal`, the other classes are overridden, causing the modal to be displayed incorrectly.
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https... | null | 2018-12-04 12:07:06+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> should be open by default', 'packages/material-ui/src/Dialog/Dialog.test.js-><Dialog /> prop: fullScreen false should not render fullScreen', '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 /> prop: PaperProps.className warns on className usage'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Dialog/Dialog.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 13,821 | mui__material-ui-13821 | ['13635'] | 182f7d8ec3f55cd64ca6fd147a94e67fb46f9dc3 | diff --git a/packages/material-ui/src/Popover/Popover.js b/packages/material-ui/src/Popover/Popover.js
--- a/packages/material-ui/src/Popover/Popover.js
+++ b/packages/material-ui/src/Popover/Popover.js
@@ -8,6 +8,7 @@ import debounce from 'debounce'; // < 1kb payload overhead when lodash/debounce
import EventListener... | diff --git a/packages/material-ui/src/Popover/Popover.test.js b/packages/material-ui/src/Popover/Popover.test.js
--- a/packages/material-ui/src/Popover/Popover.test.js
+++ b/packages/material-ui/src/Popover/Popover.test.js
@@ -845,4 +845,20 @@ describe('<Popover />', () => {
assert.strictEqual(wrapper.find(Trans... | [Popover] Broken onEntering event propagation
<!--- 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 shoul... | Upon further investigation it seems like this only happens when Select has provided `MenuProps` -> `TransitionProps` -> `onEntering` prop.
In my codesandbox reproduction, when I remove `onEntering: this.onSelectTransitionEntering.bind(this),`, then it starts to work as it should.
This still is a problem for our ... | 2018-12-05 17:39:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ["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 /> paper should have a elevation prop passed down', 'packages/material-ui/src/Popover/Popover.test.js-><Popover /> positi... | ['packages/material-ui/src/Popover/Popover.test.js-><Popover /> prop: TransitionProp should fire Popover transition event callbacks'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Popover/Popover.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/Popover/Popover.js->program->class_declaration:Popover->method_definition:render"] |
mui/material-ui | 13,828 | mui__material-ui-13828 | ['13713'] | fb3a64f045ba5e2bb4255b792a9a7e506f9d510d | diff --git a/packages/material-ui/src/LinearProgress/LinearProgress.d.ts b/packages/material-ui/src/LinearProgress/LinearProgress.d.ts
--- a/packages/material-ui/src/LinearProgress/LinearProgress.d.ts
+++ b/packages/material-ui/src/LinearProgress/LinearProgress.d.ts
@@ -13,6 +13,8 @@ export type LinearProgressClassKey ... | diff --git a/packages/material-ui/src/LinearProgress/LinearProgress.test.js b/packages/material-ui/src/LinearProgress/LinearProgress.test.js
--- a/packages/material-ui/src/LinearProgress/LinearProgress.test.js
+++ b/packages/material-ui/src/LinearProgress/LinearProgress.test.js
@@ -25,9 +25,10 @@ describe('<LinearProgr... | [LinearProgress] Add more classes keys
<!--- Provide a general summary of the feature in the Title above -->
There are some useful classes that could be easily added along with a potential class rename to avoid confusion
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To ... | @szrharrison I'm proposing the following approach:
- We add the `indeterminate` and `determinate` style rules (classes) to the root element, applied when the right variant property is provided.
- `query` is already applied on the root element, no need to change anything.
- You can already use the `bar` style rule to... | 2018-12-05 22:39:42+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should render for the primary color', 'packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should render with the user and root classes', 'packages/material-ui/src/LinearProgress/LinearProgress.test.js-><... | ['packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should set width of bar1 on determinate variant', 'packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should render with determinate classes for the primary color', 'packages/material-ui/src/LinearProgre... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/LinearProgress/LinearProgress.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/LinearProgress/LinearProgress.js->program->function_declaration:LinearProgress"] |
mui/material-ui | 13,848 | mui__material-ui-13848 | ['13841'] | 808adda4619a592f29bcbdfdd94854e79803cd66 | diff --git a/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.d.ts b/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.d.ts
--- a/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.d.ts
+++ b/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.d.ts
@@ -8,6 +8,7 @@ export interf... | diff --git a/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js b/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js
--- a/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js
+++ b/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js
@@ -39,6 +39,12 @... | [Speed dial] Change tooltip background and color using TooltipProps
<!--- 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.
-->
<!-- Checke... | @JoeKyy We have a demonstrate how to change the tooltip color in https://material-ui.com/demos/tooltips#customized-tooltips. It should help.
@oliviertassinari I think he wants a pass through prop added to `SpeedDialAction` to affect all tooltip props
Exactly!
| 2018-12-07 00:01:59+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js-><SpeedDialAction /> should render a Button', 'packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js-><SpeedDialAction /> should render the Button with the button and buttonClosed classes', 'packages/material-ui-lab/src/SpeedDialActio... | ['packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js-><SpeedDialAction /> should be able to change the Tooltip classes'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.js->program->class_declaration:SpeedDialAction->method_definition:render"] |
mui/material-ui | 13,853 | mui__material-ui-13853 | ['13812'] | 29eae3a3da597488d615077081b630c1fa2ad81f | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '95 KB',
+ limit: '94.9 KB',
},
{
name: 'The... | diff --git a/packages/material-ui/src/Tabs/ScrollbarSize.test.js b/packages/material-ui/src/Tabs/ScrollbarSize.test.js
--- a/packages/material-ui/src/Tabs/ScrollbarSize.test.js
+++ b/packages/material-ui/src/Tabs/ScrollbarSize.test.js
@@ -7,7 +7,6 @@ import ScrollbarSize from './ScrollbarSize';
describe('<ScrollbarS... | tabs scrollable bugs
tabs scrollable bugs after open or close devtools
| @maystrenkoYurii do you have a minimal reproducible example?
Why? These bugs are also on your site, on the example tabs page. Open your site, go to tab tabs, open and close the developer panel and watch the bugs.
https://material-ui.com/demos/tabs/
@maystrenkoYurii I don't see the issues you described. Pleas fill o... | 2018-12-07 23:36:34+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Tabs/ScrollbarSize.test.js-><ScrollbarSize /> prop: onChange should not call on second resize event', 'packages/material-ui/src/Tabs/ScrollbarSize.test.js-><ScrollbarSize /> mount should call on initial load', 'packages/material-ui/src/Tabs/ScrollbarSize.test.js-><ScrollbarSize /> prop: onCha... | ['packages/material-ui/src/Tabs/ScrollbarSize.test.js-><ScrollbarSize /> mount should not call on initial load'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tabs/ScrollbarSize.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 3 | 2 | 5 | false | false | ["packages/material-ui/src/Tabs/ScrollbarSize.js->program->class_declaration:ScrollbarSize->method_definition:render", "packages/material-ui/src/Tabs/ScrollbarSize.js->program->class_declaration:ScrollbarSize->method_definition:componentDidMount", "packages/material-ui/src/Tabs/Tabs.js->program->class_declaration:Tabs"... |
mui/material-ui | 13,857 | mui__material-ui-13857 | ['13844'] | 02ccf5e102938e1cd14cce8dadedd98e44002d9b | diff --git a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js
--- a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js
+++ b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js
@@ -34,7 +34,6 @@ cla... | diff --git a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js
--- a/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js
+++ b/packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js
@... | ToggleButtonGroup onChange should pass empty array instead of null
<!--- Provide a general summary of the feature in the Title above -->
Mixing the types (`Array` / `null`) adds unnecessary complexity.
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate iss... | null | 2018-12-08 17:38:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js-><ToggleButtonGroup /> prop: onChange exclusive should be a single value when value is toggled on', 'packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js-><ToggleButtonGroup /> prop: onChange exclusive should be a single valu... | ['packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js-><ToggleButtonGroup /> prop: onChange non exclusive should be an empty array when current value is toggled off'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui-lab/src/ToggleButtonGroup/ToggleButtonGroup.js->program->class_declaration:ToggleButtonGroup"] |
mui/material-ui | 13,899 | mui__material-ui-13899 | ['12390'] | 64714e6b367632e3acb973ef3ae2a28eed25aadd | diff --git a/docs/src/pages/style/color/ColorDemo.js b/docs/src/pages/style/color/ColorDemo.js
--- a/docs/src/pages/style/color/ColorDemo.js
+++ b/docs/src/pages/style/color/ColorDemo.js
@@ -43,7 +43,7 @@ const styles = theme => ({
function ColorDemo(props) {
const { classes, data, theme } = props;
- const prima... | 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
@@ -216,11 +216,21 @@ describe('createPalette()', () => {
});
it('sho... | Make theme.palette.augmentColor() pure
**We love the theme object, but starting to see how it could be extended.**
• In most cases, a primary, secondary, error and grey color palette will support most applications.
• I am having to add custom colors to the theme to cover a warning situation.
Rather than extend t... | @designjudo Here is how we handle the problem on our product.
Material-UI is exposing the `theme.palette.augmentColor` function for this use case. The API isn't perfect (mutable) nor it's documented yet 🙈. So, you should be able to add a warning color into your palette like this:
```jsx
import { createMuiTheme } fr... | 2018-12-13 18:02:00+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 calculate light and dark colors if not provided'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/styles/createPalette.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 7 | 0 | 7 | false | false | ["packages/material-ui/src/styles/createPalette.js->program->function_declaration:createPalette->function_declaration:augmentColor", "packages/material-ui/src/styles/createPalette.js->program->function_declaration:createPalette", "packages/material-ui/src/styles/createPalette.js->program->function_declaration:createPal... |
mui/material-ui | 13,931 | mui__material-ui-13931 | ['13926'] | 5773bd0b4714a43bc11ef4bf509207a5336fd112 | diff --git a/docs/src/pages/demos/buttons/CustomizedButtons.js b/docs/src/pages/demos/buttons/CustomizedButtons.js
--- a/docs/src/pages/demos/buttons/CustomizedButtons.js
+++ b/docs/src/pages/demos/buttons/CustomizedButtons.js
@@ -7,10 +7,6 @@ import purple from '@material-ui/core/colors/purple';
import green from '@m... | diff --git a/packages/material-ui/src/ListItemText/ListItemText.test.js b/packages/material-ui/src/ListItemText/ListItemText.test.js
--- a/packages/material-ui/src/ListItemText/ListItemText.test.js
+++ b/packages/material-ui/src/ListItemText/ListItemText.test.js
@@ -52,7 +52,7 @@ describe('<ListItemText />', () => {
... | Button text is not vertically aligned
I feel like the buttons in material ui v3.6.2 do not have the text vertically aligned while rendering on Chrome 70.
I think that that they looked fine in material-ui v0.x but in the recent material-ui versions they are a bit taller and have a "chin" under the text.
Here are s... | @adipascu Yes, you are right, the height of the button component is wrong 😱:
It should be 36px over 37px. I propose the following fix:
```diff
export const styles = them... | 2018-12-17 23:21:54+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> prop: primary should use the children prop as primary node', 'packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> should render with the user and root classes', 'packages/material-ui/src/ListItemText/ListItemText.tes... | ['packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> prop: primary should render primary text', 'packages/material-ui/src/ListItemText/ListItemText.test.js-><ListItemText /> prop: disableTypography should wrap children in `<Typography/>` by default'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ListItemText/ListItemText.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 3 | 0 | 3 | false | false | ["packages/material-ui/src/styles/createTypography.js->program->function_declaration:createTypography", "packages/material-ui/src/ListItemText/ListItemText.js->program->function_declaration:ListItemText", "docs/src/pages/demos/buttons/CustomizedButtons.js->program->function_declaration:CustomizedInputs"] |
mui/material-ui | 14,023 | mui__material-ui-14023 | ['12996'] | abb0f18a78d933bd9ea9f16c2991fd512527c80f | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '95.2 KB',
+ limit: '95.3 KB',
},
{
name: 'T... | diff --git a/packages/material-ui/src/InputAdornment/InputAdornment.test.js b/packages/material-ui/src/InputAdornment/InputAdornment.test.js
--- a/packages/material-ui/src/InputAdornment/InputAdornment.test.js
+++ b/packages/material-ui/src/InputAdornment/InputAdornment.test.js
@@ -1,84 +1,183 @@
import React from 're... | [InputAdornment] Automatically inherit the variant
<!--- 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... | Seems like you forgot the TextFields in the codesandbox.
Ah you're right I guess I forgot to press save. I updated the link, should be working now!
https://codesandbox.io/s/43y02726z7
@Anwardo It's not following the documentation:
```diff
InputProps={{
startAdornment: (
- ... | 2018-12-28 19:25:02+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> prop: variant should have the filled root and class when variant is filled', 'packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> should render children', 'packages/material-ui/src/InputAdornment/InputAdo... | ['packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> prop: variant warnings should warn if the variant supplied is equal to the variant inferred', "packages/material-ui/src/InputAdornment/InputAdornment.test.js-><InputAdornment /> prop: variant should inherit the TextField's variant", "p... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputAdornment/InputAdornment.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 5 | 0 | 5 | false | false | ["docs/src/pages/demos/text-fields/FilledInputAdornments.js->program->class_declaration:FilledInputAdornments->method_definition:render", "packages/material-ui/src/InputAdornment/InputAdornment.js->program->function_declaration:InputAdornment", "docs/src/pages/demos/text-fields/FormattedInputs.hooks.js->program->functi... |
mui/material-ui | 14,036 | mui__material-ui-14036 | ['10831'] | f946f19a5c8a6b38759e02bd86c9b77e89232caa | 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
@@ -68,7 +68,6 @@ export const styles = theme => {
transition: trackTransitions,
'&$activated':... | diff --git a/packages/material-ui/src/Fade/Fade.test.js b/packages/material-ui/src/Fade/Fade.test.js
--- a/packages/material-ui/src/Fade/Fade.test.js
+++ b/packages/material-ui/src/Fade/Fade.test.js
@@ -87,7 +87,6 @@ describe('<Fade />', () => {
);
assert.deepEqual(wrapper.find('div').props().style, {
... | What the will-change issue might be?
<!--- 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 thi... | @leedstyh We don't use the `willChange` property much: https://github.com/mui-org/material-ui/search?utf8=%E2%9C%93&q=willchange&type=. Can you provide a isolated reproduction example? The warning could come from a third party library.
Not appears every time, so I'll close this now. Will ping you back here if I have mo... | 2018-12-30 14:27:39+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Fade/Fade.test.js-><Fade /> should render a Transition', 'packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> transition lifecycle handleExit() should set the style properties', 'packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> transition lifecycle handleEnter() should set the style prop... | ['packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> prop: appear should work when initially hidden', 'packages/material-ui/src/Fade/Fade.test.js-><Fade /> prop: appear should work when initially hidden'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Fade/Fade.test.js packages/material-ui/src/Zoom/Zoom.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Fade/Fade.js->program->class_declaration:Fade->method_definition:render", "packages/material-ui/src/Zoom/Zoom.js->program->class_declaration:Zoom->method_definition:render"] |
mui/material-ui | 14,121 | mui__material-ui-14121 | ['14105'] | 86199ea9ad5c15655618fb89cdca123177920928 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '96 KB',
+ limit: '96.2 KB',
},
{
name: 'The... | 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
@@ -163,4 +163,213 @@ describe('<Badge />', () => {
);
});
});
+
+ describe('prop: showZero', () ... | Badge bug
Badge bug. Width badge is not chenged for size content. I fix with my style.
| @maystrenkoYurii Thank you for sharing this problem. I agree. I think that we can apply the following changes:
```diff
@@ -5,7 +5,7 @@ import { componentPropType } from '@material-ui/utils';
import withStyles from '../styles/withStyles';
import { capitalize } from '../utils/helpers';
-const RADIUS = 11;
+cons... | 2019-01-08 22:52:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Badge/Badge.test.js-><Badge /> renders children and have primary styles', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> renders children and overwrite root styles', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> renders children and have secondary styles', 'packages/mater... | ['packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: showZero should default to false', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: showZero should render with the invisible class when false and badgeContent is 0', 'packages/material-ui/src/Badge/Badge.test.js-><Badge /> prop: max should d... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Badge/Badge.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 3 | 0 | 3 | false | false | ["docs/src/pages/demos/badges/BadgeVisibility.hooks.js->program->function_declaration:BadgeVisibility", "packages/material-ui/src/Badge/Badge.js->program->function_declaration:Badge", "docs/src/pages/demos/badges/BadgeVisibility.js->program->class_declaration:BadgeVisibility->method_definition:render"] |
mui/material-ui | 14,212 | mui__material-ui-14212 | ['13865'] | 7a43dbace0a96a2f4e811b1907bac0635da31278 | diff --git a/.size-limit.js b/.size-limit.js
--- a/.size-limit.js
+++ b/.size-limit.js
@@ -22,7 +22,7 @@ module.exports = [
name: 'The size of the @material-ui/core modules',
webpack: true,
path: 'packages/material-ui/build/index.js',
- limit: '95.2 KB',
+ limit: '95.3 KB',
},
{
name: 'T... | 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
@@ -62,6 +62,16 @@ describe('<Menu> integration', () => {
assert.strictEqual(docum... | [MenuList] Support Home/End keys and wraparound
It would be nice if `MenuList` supported the optional wraparound for the up/down arrow keyboard navigation as described in the [ARIA keyboard navigation guidelines for menus](https://www.w3.org/TR/wai-aria-practices-1.1/#menu). Same for having the Home/End keys move to th... | I'm not sure to understand what you mean. How is this not working as we are speaking? Following our issue template would help :).
@eric-parsons I agree with @oliviertassinari - deleting the issue template is a bit selfish. We put it there to make it easier for you to provide the information we need to help solve your ... | 2019-01-17 02:42:08+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/test/integration/Menu.test.js-><Menu> integration mounted open should keep focus on the last item when a key with no associated action is pressed', 'packages/material-ui/test/integration/Menu.test.js-><Menu> integration mounted open should change focus to the 2nd item when up arrow is pressed', '... | ['packages/material-ui/test/integration/Menu.test.js-><Menu> integration mounted open should switch focus from the 3rd item to the 1st item when home key is pressed'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/test/integration/Menu.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/MenuList/MenuList.js->program->class_declaration:MenuList"] |
mui/material-ui | 14,266 | mui__material-ui-14266 | ['14231'] | 345be3452c528fe46b8be965b3a8846dffedf50d | diff --git a/docs/src/modules/components/MarkdownDocsContents.js b/docs/src/modules/components/MarkdownDocsContents.js
--- a/docs/src/modules/components/MarkdownDocsContents.js
+++ b/docs/src/modules/components/MarkdownDocsContents.js
@@ -33,13 +33,13 @@ function MarkdownDocsContents(props) {
## API
${headers.compo... | 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
@@ -94,6 +94,11 @@ describe('<TextField />', () => {
assert.strictEqual(... | [TextField] helperText accessibility
`<TextField />` property `helperText` is not accessible. I believe `aria-describedby` should be applied to the `InputElement` and not to the `FormControl` 🤔
- [x] This is not a v0.x issue. <!-- (v0.x is no longer maintained) -->
- [x] I have searched the [issues](https://github... | @enagy-earnup I think that you are right: https://www.w3.org/TR/WCAG20-TECHS/ARIA21.html. How do you think that we should solve the issue? Fix the demos with a documentation section on the accessible error messages?
@oliviertassinari moving the `aria-describedby` to the input solves the accessibility issue - I just tes... | 2019-01-22 13:15:09+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> shallow structure should have an Input as the only child', 'packages/material-ui/src/TextField/TextField.test.js-><TextField /> shallow structure should forward the fullWidth prop to Input', 'packages/material-ui/src/TextField/TextField.test.js-><Tex... | ['packages/material-ui/src/TextField/TextField.test.js-><TextField /> shallow with a helper text should add accessibility labels to the input'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 11 | 0 | 11 | false | false | ["packages/material-ui/src/useMediaQuery/unstable_useMediaQuery.js->program->function_declaration:unstable_useMediaQuery", "packages/material-ui-styles/src/makeStyles.js->program->function_declaration:makeStyles", "docs/src/pages/demos/text-fields/InputAdornments.hooks.js->program->function_declaration:InputAdornments"... |
mui/material-ui | 14,282 | mui__material-ui-14282 | ['14233'] | 85e13ec9dcb17fd0665784e2173580a3682e5a05 | diff --git a/docs/src/pages/demos/expansion-panels/CustomizedExpansionPanel.js b/docs/src/pages/demos/expansion-panels/CustomizedExpansionPanel.js
--- a/docs/src/pages/demos/expansion-panels/CustomizedExpansionPanel.js
+++ b/docs/src/pages/demos/expansion-panels/CustomizedExpansionPanel.js
@@ -62,7 +62,11 @@ class Cust... | 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
@@ -26,7 +26,7 @@ describe('<ExpansionPan... | [Accordion] square prop not working
As tittle says when i want to set square property to true on ExpansionPanel, nothing changes. Panel is still rounded.
| Tech | Version |
|--------------|---------|
| Material-UI | v3.9.0 |
| React | 16.7.0 |
| Browser | Chrome |
| @rpkRED Yes, you are right, the square property is ignored. We should be able to change the expansion panel implementation a bit to make it work. What do you think of these changes?
```diff
--- a/packages/material-ui/src/ExpansionPanel/ExpansionPanel.js
+++ b/packages/material-ui/src/ExpansionPanel/ExpansionPanel.... | 2019-01-23 06:01:14+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js-><ExpansionPanel /> should handle the expanded prop', 'packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js-><ExpansionPanel /> when undefined onChange and controlled should not call the onChange', 'packages/material-ui/src/ExpansionPanel/Expans... | ['packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js-><ExpansionPanel /> should render and have isControlled set to false'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ExpansionPanel/ExpansionPanel.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 2 | 0 | 2 | false | false | ["docs/src/pages/demos/expansion-panels/CustomizedExpansionPanel.js->program->class_declaration:CustomizedExpansionPanel->method_definition:render", "packages/material-ui/src/ExpansionPanel/ExpansionPanel.js->program->class_declaration:ExpansionPanel->method_definition:render"] |
mui/material-ui | 14,305 | mui__material-ui-14305 | ['13962'] | a02ade087363576ca7d6631db39ec88401aa42d3 | diff --git a/docs/scripts/buildIcons.js b/docs/scripts/buildIcons.js
--- a/docs/scripts/buildIcons.js
+++ b/docs/scripts/buildIcons.js
@@ -30,5 +30,5 @@ Promise.all(promises).catch(err => {
setTimeout(() => {
console.log(err);
throw err;
- }, 0);
+ });
});
diff --git a/docs/src/pages/demos/progress/Dela... | 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,3 +1,5 @@
+/* eslint-disable react/no-multi-comp */
+
import React from 'react';
import { assert } from '... | Modal manager crashes while switching between popovers
Modal manage crashes on this [line](https://github.com/mui-org/material-ui/blob/f7c1a216cf396f0f942e0fe1c2e9a2d6796b716b/packages/material-ui/src/Modal/ModalManager.js#L130) while jumping between popovers.
https://codesandbox.io/s/049kpv0kzv
<!-- Checked chec... | I manage to fix the issue by removing the workaround we did in order to trigger modal to rerender
[https://codesandbox.io/s/45v78lx9](https://codesandbox.io/s/45v78lx9)
| 2019-01-26 00:03:24+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> backdrop should attach a handler to the backdrop that fires onClose', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> handleKeyDown() should not be call when default... | ['packages/material-ui/src/Portal/Portal.test.js-><Portal /> should work with a high level component like the Select', 'packages/material-ui/src/Portal/Portal.test.js-><Portal /> should call onRendered after child componentDidUpdate', 'packages/material-ui/src/Portal/Portal.test.js-><Portal /> prop: disablePortal shoul... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Portal/Portal.test.js packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 3 | 3 | 6 | false | false | ["packages/material-ui/src/Portal/Portal.js->program->class_declaration:Portal->method_definition:componentWillUnmount", "docs/src/pages/demos/progress/DelayingAppearance.js->program->class_declaration:DelayingAppearance", "docs/src/pages/demos/progress/DelayingAppearance.hooks.js->program->function_declaration:Delayin... |
mui/material-ui | 14,350 | mui__material-ui-14350 | ['13916'] | 45079440a6151358e69ab23e8e8aeed71cef95ce | 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
@@ -1,7 +1,7 @@
import React from 'react';
import PropTypes from 'prop-types';
import classNames from 'cla... | diff --git a/packages/material-ui/src/ListItem/ListItem.test.js b/packages/material-ui/src/ListItem/ListItem.test.js
--- a/packages/material-ui/src/ListItem/ListItem.test.js
+++ b/packages/material-ui/src/ListItem/ListItem.test.js
@@ -1,6 +1,7 @@
import React from 'react';
import { assert } from 'chai';
import { get... | Improve documentation for `ListItem` and `ListItemSecondaryAction`
Improve the documentation for how `ListItemSecondaryAction` components work within `ListItem` components.
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate issues we ask you to check off th... | null | 2019-01-30 11:48:26+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/ListItem/ListItem.test.js-><ListItem /> should disable the gutters', 'packages/material-ui/src/ListItem/ListItem.test.js-><ListItem /> should render a li', 'packages/material-ui/src/ListItem/ListItem.test.js-><ListItem /> prop: button should render a div', 'packages/material-ui/src/ListItem/L... | ['packages/material-ui/src/ListItem/ListItem.test.js-><ListItem /> secondary action warnings warns if it cant detect the secondary action properly'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/ListItem/ListItem.test.js --reporter /testbed/custom-reporter.js --exit | Feature | true | false | false | false | 0 | 0 | 0 | false | false | [] |
mui/material-ui | 14,364 | mui__material-ui-14364 | ['14360'] | b5d9b243d30a879ab33e53bda4c6553402d99e39 | diff --git a/packages/material-ui/src/InputAdornment/InputAdornment.js b/packages/material-ui/src/InputAdornment/InputAdornment.js
--- a/packages/material-ui/src/InputAdornment/InputAdornment.js
+++ b/packages/material-ui/src/InputAdornment/InputAdornment.js
@@ -6,6 +6,7 @@ import warning from 'warning';
import Typogr... | 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
@@ -12,6 +12,8 @@ import FormControlContext from '../FormControl/FormControlConte... | Select inside InputAdornment causes crash with material-ui/core 3.9.1 (works with 3.9.0)
<!--- Provide a general summary of the issue in the Title above -->
We use a Select as InputAdornment to let users choose a unit. It worked fine until material-ui/core 3.9.0, but now crashes the whole application.
<!--
T... | @joshwooding People are full of imagination 🔮. The prediction comes true. Now it's great. We have a reproduction.
@mtidei Thank you for the report. The fix is simple. We just need to make
https://github.com/mui-org/material-ui/blob/4422ce889293268cf7aaa8b1f5e63d465501a05f/packages/material-ui/src/InputBase/InputBa... | 2019-01-31 19:23:43+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputComponent should inject onBlur and onFocus', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> mount should be able to access the native textarea', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> con... | ['packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: startAdornment, prop: endAdornment should allow a Select as an adornment', 'packages/material-ui/src/InputBase/InputBase.test.js-><InputBase /> prop: inputRef should be able to return the input node via a ref object', 'packages/material-ui/src/... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/InputBase/InputBase.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/InputAdornment/InputAdornment.js->program->function_declaration:InputAdornment"] |
mui/material-ui | 14,391 | mui__material-ui-14391 | ['14387'] | 2dedcc12fda827a9bbb0bece2f94aa0695e73a7c | diff --git a/packages/material-ui/src/styles/colorManipulator.js b/packages/material-ui/src/styles/colorManipulator.js
--- a/packages/material-ui/src/styles/colorManipulator.js
+++ b/packages/material-ui/src/styles/colorManipulator.js
@@ -31,7 +31,7 @@ function clamp(value, min = 0, max = 1) {
* @param {string} color... | diff --git a/packages/material-ui/src/styles/colorManipulator.test.js b/packages/material-ui/src/styles/colorManipulator.test.js
--- a/packages/material-ui/src/styles/colorManipulator.test.js
+++ b/packages/material-ui/src/styles/colorManipulator.test.js
@@ -2,8 +2,9 @@ import { assert } from 'chai';
import consoleErr... | getLuminance method use incorrect coefficient for calculations
<!-- 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 ... | > According to this wiki page this line
We are using the WCGA 2 guidelines: https://www.w3.org/TR/WCAG20-TECHS/G17.html#G17-tests. cc @mbrookes
The proposed value is taken from the IEC 61966-2-1 specification.
No idea what standard we should follow.
The luminance value is used to assess accessibility, so I belie... | 2019-02-03 00:16:32+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/styles/colorManipulator.test.js->utils/colorManipulator getLuminance returns a valid luminance for rgb white', 'packages/material-ui/src/styles/colorManipulator.test.js->utils/colorManipulator recomposeColor converts a decomposed rgb color object to a string` ', 'packages/material-ui/src/styl... | ['packages/material-ui/src/styles/colorManipulator.test.js->utils/colorManipulator hexToRgb converts a short hex color to an rgb color` ', 'packages/material-ui/src/styles/colorManipulator.test.js->utils/colorManipulator getLuminance returns a valid luminance from an hsl color', 'packages/material-ui/src/styles/colorMa... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/styles/colorManipulator.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 13 | 0 | 13 | false | false | ["packages/material-ui/src/styles/colorManipulator.js->program->function_declaration:darken", "packages/material-ui/src/styles/colorManipulator.js->program->function_declaration:convertHexToRGB", "packages/material-ui/src/styles/colorManipulator.js->program->function_declaration:decomposeColor", "packages/material-ui/s... |
mui/material-ui | 14,452 | mui__material-ui-14452 | ['14294'] | 64e19ddf97ac942474b584370d5dd5d2dec3b910 | 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
@@ -129,7 +129,16 @@ class SelectInput extends React.Component {
return;
}
- if ([' ', '... | 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
@@ -220,7 +220,7 @@ describe('<SelectInput />', () => {
assert.strictEqual(han... | Open Select menu by pressing Enter button when Select in focus
<!--- 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 c... | > We should be able to open Select Menu when Select is in focus by pressing Enter keyboard
@oknechirik This is a Windows-only behavior. It won't happen on MacOS. I think that we can add the `Enter` key when we detect a windows platform:
https://github.com/mui-org/material-ui/blob/90631bcdeb3bdfbf82f94e71ea2ae874828... | 2019-02-07 11:29:04+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ["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 /> prop: onChange 'should open menu when pressed Enter key on select"] | ['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'] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Select/SelectInput.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Select/SelectInput.js->program->class_declaration:SelectInput"] |
mui/material-ui | 14,461 | mui__material-ui-14461 | ['14456'] | 20c84d193f9ae6f53cd8da37073dc3a1a6cc144a | 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
@@ -564,13 +564,7 @@ class Slider extends React.Component {
return (
<Component
- role="... | 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
@@ -1,7 +1,12 @@
import React from 'react';
import { spy } from 'sinon';
import { asse... | [Slider] - Slider handle is a button without an accessible name
<!--- Provide a general summary of the issue in the Title above -->
Lighthouse gives the following warning:
> When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers
... | Thank you for reporting this.
I think we're currently using the [`slider` role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_slider_role) wrong. It should be attached to the handle (which is the button) and not the wrapper.
I wonder what semantics should be attached t... | 2019-02-08 10:01:56+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> unmount should not have global event listeners registered after unmount', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> should only listen to changes from the same touchpoint', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> prop: disabled should signal that it is disabled', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> prop: disabled should render thumb with the disabled classes', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> prop: slider ... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 3 | 0 | 3 | false | false | ["packages/material-ui/src/test-utils/findOutermostIntrinsic.js->program->function_declaration:findOutermostIntrinsic", "packages/material-ui/src/test-utils/findOutermostIntrinsic.js->program->function_declaration:wrapsIntrinsicElement", "packages/material-ui-lab/src/Slider/Slider.js->program->class_declaration:Slider-... |
mui/material-ui | 14,465 | mui__material-ui-14465 | ['12632'] | aad72ed7af8f49354ff261d96a3cc97b4ff500de | diff --git a/packages/material-ui/src/Collapse/Collapse.js b/packages/material-ui/src/Collapse/Collapse.js
--- a/packages/material-ui/src/Collapse/Collapse.js
+++ b/packages/material-ui/src/Collapse/Collapse.js
@@ -21,6 +21,11 @@ export const styles = theme => ({
height: 'auto',
overflow: 'visible',
},
+ ... | diff --git a/packages/material-ui/src/Fade/Fade.test.js b/packages/material-ui/src/Fade/Fade.test.js
--- a/packages/material-ui/src/Fade/Fade.test.js
+++ b/packages/material-ui/src/Fade/Fade.test.js
@@ -87,6 +87,7 @@ describe('<Fade />', () => {
);
assert.deepEqual(wrapper.find('div').props().style, {
... | [Accordion] Make follow accessibly standards
<!--- Provide a general summary of the feature in the Title above -->
Currently, if you have a link of any kind inside your panel and you tab through the page, the tab sequence will tab to hidden items in the closed expansions. The tab sequence should skip links inside of c... | @salientknight I believe it's a duplicate of #10569. There is a known workaround, as far as I remember, the issue is about improving the API. | 2019-02-08 14:06:19+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Slide/Slide.test.js-><Slide /> transition lifecycle handleEntering() should reset the translate3d', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> transition lifecycle handleExiting() should set element transform and transition according to the direction', 'packages/material-ui/src/... | ['packages/material-ui/src/Zoom/Zoom.test.js-><Zoom /> prop: appear should work when initially hidden: appear=false', 'packages/material-ui/src/Fade/Fade.test.js-><Fade /> prop: appear should work when initially hidden, appear=true', 'packages/material-ui/src/Slide/Slide.test.js-><Slide /> mount should work when initia... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Slide/Slide.test.js packages/material-ui/src/Fade/Fade.test.js packages/material-ui/src/Zoom/Zoom.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | true | false | false | 6 | 0 | 6 | false | false | ["packages/material-ui/src/Grow/Grow.js->program->class_declaration:Grow->method_definition:render", "packages/material-ui/src/Slide/Slide.js->program->class_declaration:Slide->method_definition:updatePosition", "packages/material-ui/src/Collapse/Collapse.js->program->class_declaration:Collapse->method_definition:rende... |
mui/material-ui | 14,475 | mui__material-ui-14475 | ['13132'] | 52040dc8b4675c1ff22af7a0e42299e4572cf58b | 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
@@ -323,15 +323,7 @@ class Slider extends React.Component {
};
handleClick = event => {
- const { ... | 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
@@ -70,6 +70,22 @@ describe('<Slider />', () => {
assert.strictEqual(handleChange.ca... | Slider's callbacks are executed in an unreliable order
The Slider's callbacks are executed in an unreliable order
## Expected Behavior
The `onDragStart`, `onChange`, `onDragEnd` callbacks should be called in a consistent order.
## Current Behavior
The callbacks are called in varying orders depending on the ... | I fear that there is no easy built-in solution for this since browsers always fire mousedown -> mouseup -> click. That's what you are seeing in the second example.
I think what you want is to debounce changes during dragging only. I think an implementation with reactive programming would be the simplest solution. Yo... | 2019-02-09 20:57:49+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> should render with the default classes', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> when mouse leaves window should move to the end', 'packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> when mouse reenters window should no... | ['packages/material-ui-lab/src/Slider/Slider.test.js-><Slider /> should call handlers'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | false | false | true | 2 | 1 | 3 | false | false | ["packages/material-ui-lab/src/Slider/Slider.js->program->class_declaration:Slider->method_definition:handleDragEnd", "packages/material-ui-lab/src/Slider/Slider.js->program->class_declaration:Slider->method_definition:calculateValueFromPercent", "packages/material-ui-lab/src/Slider/Slider.js->program->class_declaratio... |
mui/material-ui | 14,496 | mui__material-ui-14496 | ['14468'] | 9ecc8db8abbfb829111d3b5c0678267827984024 | 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
@@ -125,15 +125,14 @@ class Tooltip extends React.Component {
};
handleFocus = event => {
- event.persist(... | 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,10 +1,12 @@
import React from 'react';
import { assert } from 'chai';
+import PropTypes f... | [Tooltip] Tooltips aren't displayed on focus on TextFields
- [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 🤔
Using a `Tooltip`... | @codeheroics Yeah, it's because we make sure the tooltip child still has the focus before opening it. We can work around the problem with:
```diff
--- a/packages/material-ui/src/Tooltip/Tooltip.js
+++ b/packages/material-ui/src/Tooltip/Tooltip.js
@@ -71,6 +71,17 @@ export const styles = theme => ({
},
});
... | 2019-02-11 15:37:08+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> mount should handle autoFocus + onFocus forwarding'] | ['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'] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Tooltip/Tooltip.js->program->class_declaration:Tooltip"] |
mui/material-ui | 14,638 | mui__material-ui-14638 | ['14538'] | cbed92306fc1a4a59599eb9c114b1d62162c0c18 | diff --git a/docs/src/pages/demos/tabs/CustomizedTabs.hooks.js b/docs/src/pages/demos/tabs/CustomizedTabs.hooks.js
--- a/docs/src/pages/demos/tabs/CustomizedTabs.hooks.js
+++ b/docs/src/pages/demos/tabs/CustomizedTabs.hooks.js
@@ -1,9 +1,32 @@
import React from 'react';
-import { makeStyles } from '@material-ui/styles... | diff --git a/packages/material-ui/src/Tab/Tab.test.js b/packages/material-ui/src/Tab/Tab.test.js
--- a/packages/material-ui/src/Tab/Tab.test.js
+++ b/packages/material-ui/src/Tab/Tab.test.js
@@ -1,7 +1,12 @@
import React from 'react';
import { assert } from 'chai';
-import { spy, stub } from 'sinon';
-import { create... | [Tabs] Awkward line height when 2 lines
- [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 🤔
![a989bab3-e062-4dcf-a679-0afd21b9b4... | Looks like this is intended for our components: https://material-ui.com/demos/tabs/#wrapped-labels. It probably changed in the spec.
Some quick hacking with `white-space: nowrap; text-overflow: ellipsis;` didn't do the trick but something along the lines should be possible.
My point isn't that it wraps, that is the ... | 2019-02-23 14:45:35+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/Tab/Tab.test.js-><Tab /> prop: textColor should support the inherit value', 'packages/material-ui/src/Tab/Tab.test.js-><Tab /> prop: label should render label', 'packages/material-ui/src/Tab/Tab.test.js-><Tab /> should render with the root class', 'packages/material-ui/src/Tab/Tab.test.js-><T... | ['packages/material-ui/src/Tab/Tab.test.js-><Tab /> prop: wrapped should add the wrapped class'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Tab/Tab.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 9 | 1 | 10 | false | false | ["docs/src/pages/demos/tabs/TabsWrappedLabel.js->program->class_declaration:TabsWrappedLabel->method_definition:render", "packages/material-ui/src/Tab/Tab.js->program->class_declaration:Tab", "docs/src/pages/demos/tabs/CustomizedTabs.js->program->class_declaration:CustomizedTabs->method_definition:render", "packages/ma... |
mui/material-ui | 14,878 | mui__material-ui-14878 | ['14696'] | bdb4baa668c38c8b14c29574eaa5e6467c0b8e9b | diff --git a/docs/src/pages/demos/selection-controls/selection-controls.md b/docs/src/pages/demos/selection-controls/selection-controls.md
--- a/docs/src/pages/demos/selection-controls/selection-controls.md
+++ b/docs/src/pages/demos/selection-controls/selection-controls.md
@@ -107,3 +107,7 @@ In this case, you can app... | diff --git a/packages/material-ui/src/RadioGroup/RadioGroup.test.js b/packages/material-ui/src/RadioGroup/RadioGroup.test.js
--- a/packages/material-ui/src/RadioGroup/RadioGroup.test.js
+++ b/packages/material-ui/src/RadioGroup/RadioGroup.test.js
@@ -5,14 +5,21 @@ import { createShallow, createMount } from '@material-u... | Broken Radio if null passed
1) Take an example from https://material-ui.com/demos/selection-controls/#radio-buttons
2) Declare state = { value: null }
3) Add componentDidMount with this.setState({ value: 'female' })
4) Run it.
No "Female" option will be chosen.
If value was set to null programmatically, then se... | @koutsenko You need to choose between the controlled and uncontrolled behavior. Check the warning in the console.
Ok, but how can i declare controlled-way that no one value is selected?
@oliviertassinari And i have no warnings in console.
@koutsenko You can set an empty string. I can confirm that no warning is raised.... | 2019-03-14 00:44:28+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> imperative focus() should focus the first non-disabled radio', 'packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> imperative focus() should not focus any radios if all are disabled', 'packages/material-ui/src/RadioGroup/RadioG... | ['packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> warnings should warn when switching from controlled to uncontrolled', 'packages/material-ui/src/RadioGroup/RadioGroup.test.js-><RadioGroup /> warnings should warn when switching between uncontrolled to controlled'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/RadioGroup/RadioGroup.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 1 | 1 | 2 | false | false | ["packages/material-ui/src/RadioGroup/RadioGroup.js->program->class_declaration:RadioGroup", "packages/material-ui/src/RadioGroup/RadioGroup.js->program->class_declaration:RadioGroup->method_definition:componentDidUpdate"] |
mui/material-ui | 14,882 | mui__material-ui-14882 | ['11289'] | 89ebedc24f97d6bc7ca2e34a00efcdd47ca16812 | diff --git a/docs/src/pages/demos/progress/CustomizedProgress.js b/docs/src/pages/demos/progress/CustomizedProgress.js
--- a/docs/src/pages/demos/progress/CustomizedProgress.js
+++ b/docs/src/pages/demos/progress/CustomizedProgress.js
@@ -1,6 +1,7 @@
import React from 'react';
import PropTypes from 'prop-types';
imp... | diff --git a/packages/material-ui/src/LinearProgress/LinearProgress.test.js b/packages/material-ui/src/LinearProgress/LinearProgress.test.js
--- a/packages/material-ui/src/LinearProgress/LinearProgress.test.js
+++ b/packages/material-ui/src/LinearProgress/LinearProgress.test.js
@@ -79,7 +79,7 @@ describe('<LinearProgre... | [Proposal][LinearProgress] impossible to maintain borderRadius when progress bar is scaled
<!--- Provide a general summary of the issue in the Title above -->
When the progress bar is below `scaleX(0.5)` the borderRadius is distorted
I was thinking about using width instead of the transform property.
> e.g.
... | @giuliogallerini I've also run into this issue. I gave this solution a shot, but the problem is that interpolation can't be done by adjusting the inline width property from what I can tell. The result is a jittery output. Back to the drawing board I guess 😞
It sounds like a good idea. I have tried the following diff:
... | 2019-03-14 10:01:48+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should render for the primary color', 'packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should render with determinate classes for the primary color', 'packages/material-ui/src/LinearProgress/LinearPro... | ['packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should set width of bar1 on determinate variant', 'packages/material-ui/src/LinearProgress/LinearProgress.test.js-><LinearProgress /> should set width of bar1 and bar2 on buffer variant'] | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/LinearProgress/LinearProgress.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["docs/src/pages/demos/progress/CustomizedProgress.js->program->function_declaration:CustomizedProgress"] |
mui/material-ui | 15,038 | mui__material-ui-15038 | ['15035'] | f207f2aa34dd52de78f8d15e1acd2ec5e0aae379 | diff --git a/packages/material-ui/src/SwipeableDrawer/SwipeArea.js b/packages/material-ui/src/SwipeableDrawer/SwipeArea.js
--- a/packages/material-ui/src/SwipeableDrawer/SwipeArea.js
+++ b/packages/material-ui/src/SwipeableDrawer/SwipeArea.js
@@ -35,7 +35,7 @@ export const styles = theme => ({
/**
* @ignore - intern... | 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
@@ -19,6 +19,20 @@ function fireB... | [SwipeableDrawer] Swipe to open works through dialogs
<!--- Provide a general summary of the issue in the Title above -->
While the `z-index` of the swipe area (added in #11031) was carefully chosen to be _below_ `Dialog`s, the opening logic still uses the body event, so you can swipe the drawer open even if a fullscr... | PR incoming… :tada: | 2019-03-24 18:58:11+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> swipe to open anchor=left should makes the drawer stay hidden', 'packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> swipe to open anchor=bottom should makes the drawer stay hidden', 'packages/mater... | ['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'] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 2 | 1 | 3 | false | false | ["packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer", "packages/material-ui/src/SwipeableDrawer/SwipeArea.js->program->function_declaration:SwipeArea", "packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer->method_d... |
mui/material-ui | 15,045 | mui__material-ui-15045 | ['15035'] | 0c0f9b1640990a93f70d9f097081341fe612af5a | 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
@@ -30,6 +30,8 @@ class SwipeableDrawer extends React... | 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
@@ -17,6 +17,20 @@ function fireB... | [SwipeableDrawer] Swipe to open works through dialogs
<!--- Provide a general summary of the issue in the Title above -->
While the `z-index` of the swipe area (added in #11031) was carefully chosen to be _below_ `Dialog`s, the opening logic still uses the body event, so you can swipe the drawer open even if a fullscr... | PR incoming… :tada: | 2019-03-25 10:31:42+00:00 | TypeScript | FROM polybench_typescript_base
WORKDIR /testbed
COPY . .
RUN . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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");' > cust... | ['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 /> swipe to open anchor=left should makes the drawer stay hidden', 'packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.test.js-><SwipeableDrawer /> swipe to open anchor=bottom should makes the drawer stay hidden', 'packages/mater... | [] | . /usr/local/nvm/nvm.sh && nvm use 14.21.3 && 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 | 1 | 1 | 2 | false | false | ["packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer", "packages/material-ui/src/SwipeableDrawer/SwipeableDrawer.js->program->class_declaration:SwipeableDrawer->method_definition:render"] |
mui/material-ui | 15,097 | mui__material-ui-15097 | ['13799'] | 2c2075e6c62fb55aacae61adad048630b2788201 | diff --git a/docs/src/pages/demos/selection-controls/CheckboxLabels.js b/docs/src/pages/demos/selection-controls/CheckboxLabels.js
--- a/docs/src/pages/demos/selection-controls/CheckboxLabels.js
+++ b/docs/src/pages/demos/selection-controls/CheckboxLabels.js
@@ -1,5 +1,5 @@
import React from 'react';
-import { makeSty... | diff --git a/packages/material-ui/src/Switch/Switch.test.js b/packages/material-ui/src/Switch/Switch.test.js
--- a/packages/material-ui/src/Switch/Switch.test.js
+++ b/packages/material-ui/src/Switch/Switch.test.js
@@ -35,22 +35,22 @@ describe('<Switch />', () => {
assert.strictEqual(wrapper.hasClass('foo'), tru... | [Switch] focused, OFF switch should have a dark grey indicator, instead of white
The Switch component has a white circle focus indicator in OFF state instead of a dark grey one.
- [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/mat... | It's not just the Switch specification that we need to update, the Radio and the Checkbox.
@oliviertassinari
The Checkbox is looking fine for me from this issue's aspect.
Actual:
Spec:
![checkbox spe... | 2019-03-28 15:04: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/Switch/Switch.test.js-><Switch /> default Switch export should render a span with the root and user classes', 'packages/material-ui/src/Switch/Switch.test.js-><Switch /> styleSheet should have the classes required for SwitchBase'] | ['packages/material-ui/src/Switch/Switch.test.js-><Switch /> default Switch export should render SwitchBase with a custom span icon with the thumb class', 'packages/material-ui/src/Switch/Switch.test.js-><Switch /> default Switch export should render the track as the 2nd child'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui/src/Switch/Switch.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 4 | 0 | 4 | false | false | ["docs/src/pages/demos/selection-controls/CustomizedSwitches.js->program->function_declaration:CustomizedSwitches", "docs/src/pages/demos/selection-controls/RadioButtons.js->program->function_declaration:RadioButtons", "docs/src/pages/demos/selection-controls/CheckboxLabels.js->program->function_declaration:CheckboxLab... |
mui/material-ui | 15,122 | mui__material-ui-15122 | ['14785'] | 03e01e36e54498ab5bde99d3c8ffadf4f742e4b7 | diff --git a/docs/src/modules/components/Demo.js b/docs/src/modules/components/Demo.js
--- a/docs/src/modules/components/Demo.js
+++ b/docs/src/modules/components/Demo.js
@@ -50,6 +50,7 @@ const styles = theme => ({
},
},
demo: {
+ margin: 'auto',
borderRadius: theme.shape.borderRadius,
backgrou... | 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
@@ -3,7 +3,7 @@ import { assert } from 'chai';
import { spy, useFakeTimers } from 'sinon... | [Snackbar] Update the implementation to match the new specification
The specification has changed many detail aspects of the snackbar. For instance, you will find different padding values, a different style on mobile, a different default animation, etc. You can find the full specification following this link: https://m... | null | 2019-03-30 17:06: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/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: TransitionComponent should use a Grow by default'] | [] | . /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 | Feature | false | true | false | false | 9 | 0 | 9 | false | false | ["docs/src/pages/demos/snackbars/CustomizedSnackbars.js->program->function_declaration:MySnackbarContentWrapper", "docs/src/pages/demos/snackbars/CustomizedSnackbars.js->program->function_declaration:CustomizedSnackbars", "docs/src/pages/demos/snackbars/ConsecutiveSnackbars.js->program->class_declaration:ConsecutiveSna... |
mui/material-ui | 15,170 | mui__material-ui-15170 | ['10825'] | 7c7645e5d5b26e78f091b56f036bfbe09cc091b0 | diff --git a/packages/material-ui/src/Collapse/Collapse.js b/packages/material-ui/src/Collapse/Collapse.js
--- a/packages/material-ui/src/Collapse/Collapse.js
+++ b/packages/material-ui/src/Collapse/Collapse.js
@@ -7,6 +7,7 @@ import Transition from 'react-transition-group/Transition';
import withStyles from '../style... | diff --git a/packages/material-ui/src/Collapse/Collapse.test.js b/packages/material-ui/src/Collapse/Collapse.test.js
--- a/packages/material-ui/src/Collapse/Collapse.test.js
+++ b/packages/material-ui/src/Collapse/Collapse.test.js
@@ -7,7 +7,6 @@ import {
createMount,
describeConformance,
getClasses,
- unwrap... | Use forwardRef
Hi,
It seems that all component functions are "hidden" when exported through the `withStyles` method.
- [ 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
Given a component *App*, us... | > this.mainDrawer.toggleDrawer()
@lazee Calling imperative methods for controlling elements is a discouraged pattern in React. I would encourage you to use an `open` like property.
> It doesn't contain the toggleDrawer function for some reason.
It's because the `withStyles()` higher order component is exposing... | 2019-04-02 23:23:30+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/Collapse/Collapse.test.js-><Collapse /> prop: collapsedHeight should be taken into account in handleExiting', '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-><Pop... | [] | . /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 packages/material-ui/src/Popper/Popper.test.js packages/material-ui/src/Collapse/Collapse.test.js packages/material-ui/src/Tooltip/Tooltip.test.js --reporter /testbed/custom-r... | Bug Fix | false | false | false | true | 3 | 1 | 4 | false | false | ["packages/material-ui/src/Collapse/Collapse.js->program->class_declaration:Collapse->method_definition:render", "packages/material-ui/src/Popper/Popper.js->program->class_declaration:Popper->method_definition:render", "packages/material-ui/src/Popper/Popper.js->program->class_declaration:Popper", "packages/material-ui... |
mui/material-ui | 15,201 | mui__material-ui-15201 | ['15186'] | 496b0ff106494eea8c1515906d3ed55683e309fb | diff --git a/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.js b/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.js
--- a/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.js
+++ b/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.js
@@ -46,7 +46,10 @@ function ThemeProvider... | diff --git a/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js b/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js
--- a/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js
+++ b/packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js
@@ -53,6 +53,42 @@ de... | Nested MuiThemeProviders cause reinsertion of styles into DOM
If you nest multiple MuiThemeProviders, after each render the style elements of the children get reinserted into DOM. This may lead to noticeable performance issues (when rendering on each keystroke etc.).
![out](https://user-images.githubusercontent.com/... | Our theme providers are not memoized which is probably the reason for the flashes. I would prefer them memoized as well but these can cause subtle bugs if you mutate the theme object directly.
I think you can fix this by wrapping the theme provider in `React.memo` and use the memoized version instead.
Wow, thank yo... | 2019-04-04 18:25:13+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/ThemeProvider/ThemeProvider.test.js->ThemeProvider should provide the theme', 'packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js->ThemeProvider warnings should warn about missing provider', 'packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js->ThemePro... | ['packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js->ThemeProvider should memoize the merged output'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-styles/src/ThemeProvider/ThemeProvider.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui-styles/src/ThemeProvider/ThemeProvider.js->program->function_declaration:ThemeProvider"] |
mui/material-ui | 15,266 | mui__material-ui-15266 | ['15180'] | dcb334e5c2fbb77a43dda7cc617868e5d9051684 | diff --git a/docs/src/pages/utils/modal/SimpleModal.js b/docs/src/pages/utils/modal/SimpleModal.js
--- a/docs/src/pages/utils/modal/SimpleModal.js
+++ b/docs/src/pages/utils/modal/SimpleModal.js
@@ -1,6 +1,5 @@
import React from 'react';
-import PropTypes from 'prop-types';
-import { withStyles } from '@material-ui/co... | 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
@@ -350,8 +350,9 @@ describe('<SpeedDial />', () => {
re... | [Tooltip/Popper]: keepMounted doesn't work when `open` updated before `Portal` updates
<!--- 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.
... | @Sharakai We most likely have the same issue with the Modal component. What do you think of this change?
```diff
--- a/packages/material-ui/src/Popper/Popper.js
+++ b/packages/material-ui/src/Popper/Popper.js
@@ -66,23 +66,6 @@ class Popper extends React.Component {
this.handleClose();
}
- static getD... | 2019-04-08 20:35: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/src/Modal/Modal.test.js-><Modal /> prop: onRendered should fire', 'packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js-><SpeedDial /> dial focus displays the actions on focus gain', 'packages/material-ui/src/Modal/Modal.test.js-><Modal /> Material-UI component API applies the className to th... | ['packages/material-ui/src/Modal/Modal.test.js-><Modal /> prop: keepMounted should remove the transition children in the DOM when closed whilst transition status is entering'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha packages/material-ui-lab/src/SpeedDial/SpeedDial.test.js packages/material-ui/src/Modal/Modal.test.js --reporter /testbed/custom-reporter.js --exit | Bug Fix | false | false | false | true | 4 | 2 | 6 | false | false | ["docs/src/pages/utils/modal/SimpleModal.js->program->class_declaration:SimpleModal->method_definition:render", "packages/material-ui/src/Modal/Modal.js->program->class_declaration:Modal->method_definition:render", "docs/src/pages/utils/modal/SimpleModal.js->program->function_declaration:SimpleModal", "packages/materia... |
mui/material-ui | 15,304 | mui__material-ui-15304 | ['15303'] | a243f67a4406d77b038f429fcd85c2d1a49d4160 | 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
@@ -91,6 +91,7 @@ class Tooltip extends React.Component {
componentDidMount() {
warning(
!this.childre... | 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
@@ -254,11 +254,11 @@ describe('<Tooltip />', () => {
});
describe('disabled button warni... | [Tooltip] Suppress "disabled button" console warning when tooltip is controlled
<!-- 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 ... | null | 2019-04-10 16:18: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/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 /> disabled button warning should not raise a warning when we are controlled'] | [] | . /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->class_declaration:Tooltip->method_definition:componentDidMount"] |
mui/material-ui | 15,331 | mui__material-ui-15331 | ['11375'] | 689170407bcc464e0866e77fd943d08d155d7436 | 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
@@ -121,7 +121,6 @@ export const styles = theme => {
/* Styles applied to the `input` element if... | 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
@@ -1,34 +1,20 @@
import React from 'react';
import { assert } from 'chai';
-import... | Enhancement on Textarea.js to allow custom ROWS_HEIGHT value
Hello,
Currently in Textarea component the ROWS_HEIGHT is static, and it has 19 as value.
Can we make it updatable based on a new prop? This will be very useful when having smaller fonts and smaller line heights.
Please see below an example where I've... | This value is only used for the initial rendering, we compute the line height for the following updates.
https://github.com/mui-org/material-ui/blob/9ec2fcf5d8349e8f074fe5e07fc4018f66b90845/packages/material-ui/src/Input/Textarea.js#L8
Do you have a reproduction? I guess we could add a property to change the value.
O... | 2019-04-12 21:18: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/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 test/regressions/tests/Textarea/Textarea.js packages/material-ui/src/InputBase/Textarea.test.js --reporter /testbed/custom-reporter.js --exit | Feature | false | false | false | true | 11 | 1 | 12 | false | false | ["packages/material-ui/src/InputBase/Textarea.js->program->class_declaration:Textarea->method_definition:render", "packages/material-ui/src/Modal/ModalManager.js->program->function_declaration:getPaddingRight", "packages/material-ui/src/InputBase/Textarea.js->program->class_declaration:Textarea->method_definition:compo... |
mui/material-ui | 15,359 | mui__material-ui-15359 | ['15262'] | 13ac4ce9239e9e3e1fdb902e3f25ad56b3497fe9 | 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
@@ -4,6 +4,7 @@ import PopperJS from 'popper.js';
import { chainPropTypes } from '@material-ui/utils';
import Portal from '... | 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
@@ -123,6 +123,20 @@ describe('<Popper />', () => {
});
});
+ describe('prop: popperOptions', ... | [Popper] onUpdate / onCreate not handled
`onUpdate` and `onCreate` options are overridden in the Popper component, making it difficult to access internal data about the popout / get lifecycle callbacks.
<!--
Thank you very much for contributing to Material-UI by creating an issue! ❤️
To avoid duplicate iss... | > I am trying to get a callback when the popup is created and get the dimensions of the rendered component.
Have you tried to provide a top div and to get a reference on it?
> > I am trying to get a callback when the popup is created and get the dimensions of the rendered component.
>
> Have you tried to provide... | 2019-04-15 20:10: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/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: popperOptions should pass all popperOptions to popperjs'] | [] | . /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 | false | true | false | 0 | 1 | 1 | false | true | ["packages/material-ui/src/Popper/Popper.js->program->class_declaration:Popper"] |
mui/material-ui | 15,360 | mui__material-ui-15360 | ['13464'] | 004bb030ae626dd85bec84d19d367cb02c75fd2c | diff --git a/docs/src/pages/demos/menus/menus.md b/docs/src/pages/demos/menus/menus.md
--- a/docs/src/pages/demos/menus/menus.md
+++ b/docs/src/pages/demos/menus/menus.md
@@ -21,8 +21,10 @@ Choosing an option should immediately ideally commit the option and close the me
## Selected menus
-If used for item selectio... | diff --git a/packages/material-ui/src/ListItem/ListItem.test.js b/packages/material-ui/src/ListItem/ListItem.test.js
--- a/packages/material-ui/src/ListItem/ListItem.test.js
+++ b/packages/material-ui/src/ListItem/ListItem.test.js
@@ -14,6 +14,10 @@ import ListItem from './ListItem';
import ButtonBase from '../ButtonB... | [Menu] Disabled MenuItems still accessible via keyboard
<!--- 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 s... | This issue is linked to #10847. We need to rework the keyboard handling focus, the implementation is both incorrect and slow.
Thanks @oliviertassinari | 2019-04-15 22:43: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/Select/SelectInput.test.js-><SelectInput /> prop: onChange 'should open menu when pressed key on select", 'packages/material-ui/src/Table/Table.test.js-><Table /> should render children', 'packages/material-ui/src/Select/SelectInput.test.js-><SelectInput /> prop: readOnly should not trigger... | ['packages/material-ui/test/integration/Menu.test.js-><Menu> integration Menu variant differences [variant=selectedMenu] second item selected and disabled', 'packages/material-ui/test/integration/Menu.test.js-><Menu> integration Menu variant differences [variant=menu] second item selected', 'packages/material-ui/test/i... | [] | . /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 packages/material-ui/test/integration/NestedMenu.test.js packages/material-ui/test/integration/MenuList.test.js packages/material-ui/src/ListItem/ListItem.test.js packages/material-ui/src/... | Bug Fix | false | true | false | false | 5 | 0 | 5 | false | false | ["packages/material-ui/src/MenuList/MenuList.js->program->function_declaration:nextItem", "packages/material-ui/src/MenuList/MenuList.js->program->function_declaration:moveFocus", "packages/material-ui-styles/src/withTheme/withTheme.js->program->function_declaration:withThemeCreator", "packages/material-ui/src/MenuList... |
mui/material-ui | 15,398 | mui__material-ui-15398 | ['15394'] | e36d33a0f3148a21065885a1d91b6fe800153a4c | 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
@@ -7,7 +7,11 @@ import withForwardedRef from '../utils/withForwardedRef';
import { setRef }... | 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
@@ -11,6 +11,17 @@ import createMuiTheme from '../styles/createMuiTheme';
const theme = create... | Tooltip reopened by browser tab switching
<!--- 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 lik... | This happens because the button is still focused. If you switch back to the tab the `focus` event is fired again.
I'm not sure we can do anything about this or even should.
@eps1lon I found solution, set disableFocusListener property, but i still think that is not expected behavor. | 2019-04-18 13:09: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/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 /> focus ignores base focus'] | [] | . /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 | 2 | 0 | 2 | false | false | ["packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip", "packages/material-ui/src/Tooltip/Tooltip.js->program->function_declaration:Tooltip->function_declaration:handleBlur"] |
mui/material-ui | 15,430 | mui__material-ui-15430 | ['15407'] | 947853d0fde0d3048f653069bb1febe6dbde9577 | diff --git a/packages/material-ui/src/FilledInput/FilledInput.js b/packages/material-ui/src/FilledInput/FilledInput.js
--- a/packages/material-ui/src/FilledInput/FilledInput.js
+++ b/packages/material-ui/src/FilledInput/FilledInput.js
@@ -243,10 +243,6 @@ FilledInput.propTypes = {
* Maximum number of rows to displa... | 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
@@ -137,10 +137,10 @@ describe('<Textarea />', () => {
assert.strictEqual(getH... | [Textarea] Remove rowsMin, use the rows prop instead
- [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 🤔
rowsMin prop should be ... | You're right TextField doesn't have a `rowsMin` prop. I don't see any harm in adding one to pass down.
Not sure if it's a bug or enhancement though. I would probably say enhancement since nothing is 'broken'.
cc @oliviertassinari
I think it does end up causing a minor bug. In my scenario we want to show a defaul... | 2019-04-21 11:46: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/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 have at least height of "rows"'] | [] | . /usr/local/nvm/nvm.sh && nvm use 18.8.0 && yarn cross-env NODE_ENV=test mocha test/regressions/tests/Textarea/Textarea.js packages/material-ui/src/InputBase/Textarea.test.js --reporter /testbed/custom-reporter.js --exit | Refactoring | false | true | false | false | 1 | 0 | 1 | true | false | ["packages/material-ui/src/InputBase/InputBase.js->program->class_declaration:InputBase->method_definition:render"] |
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.