React Modal makes page goes down
Don't know why when i click to open the modal the main screen goes down as the modal goes on top of it:
https://github.com/RodPin/Modal-with-Redux
reactjs redux modal-dialog
add a comment |
Don't know why when i click to open the modal the main screen goes down as the modal goes on top of it:
https://github.com/RodPin/Modal-with-Redux
reactjs redux modal-dialog
add a comment |
Don't know why when i click to open the modal the main screen goes down as the modal goes on top of it:
https://github.com/RodPin/Modal-with-Redux
reactjs redux modal-dialog
Don't know why when i click to open the modal the main screen goes down as the modal goes on top of it:
https://github.com/RodPin/Modal-with-Redux
reactjs redux modal-dialog
reactjs redux modal-dialog
asked Nov 25 '18 at 19:07
RodrigoRodrigo
384
384
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I've gone ahead and refactored your application. You have a lot of mistakes that are holding your application back.
Working example: https://codesandbox.io/s/xj553k7nno
Please read the following notes carefully:
- Use the npm package
react-redux(documentation) for connecting and dispatching toredux
- Separate your
containersfrom yourcomponents: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0
- When using
prop-types, I'd recommend definingpropTypesoutside of your class (I prefer it out of theclassorfunctionand before or after theexport). See this for more details. - Create
actionsthat manipulate Redux'sstateand createtypesthat handle whatstateto manipulate. - Common convention for Redux
actionsis toreturnatypeandpayload(although sometimes apayloadmay not be necessary) and for allreducersto expect thattypeandpayloadfrom the action. - Use
switchstatements instead of nestedifandelsestatements for yourreducers. - When
importing please follow this order:
- 1.) Node Modules
- 2.) Components/Containers/Actions/Reducers/Helper functions
- 3.) Stylesheets
- Do not nest invalid HTML elements:
<p><div/></p>(divcan not appear as achildofp) - Do not use vague prop names:
close,open, ...etc. Instead be more declarative:closeModal,openModal, ...etc. - Do not use underscores
_as this is not a common JavaScript naming convention - Reduce repetitive code with reusable components (for example:
ModalColor)! - In this example, React
stateis not needed to update Redux'sstate. Redux can control its ownstatevia theactionsandreducers. - Use
<Fragment></Fragment>or<></>when you need to encapsulate JSX elements that don't need a containing HTML element.
Simplify your application structure:
├── build
| ├── css
| | ├── main.[contenthash:8].css
| | └── main.[contenthash:8].css.map
| ├── js
| | ├── main.[hash].js
| | └── main.[hash].js.map
| ├── media
| | └── [hash].[ext]
| └── favicon.ico
| └── index.html
|
├── public
| ├── favicon.ico
| └── index.html
|
├── src
| ├── actions
| ├── components
| ├── containers
| ├── images
| ├── reducers
| ├── routes
| ├── store
| ├── styles (global)
| ├── tests
| ├── types
| ├── utils
| ├── index.js
| ├── serviceWorker.js
| └── setupTests.js
|
├── .gitignore
├── README.md
├── package.lock.json
└── package.json
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53470926%2freact-modal-makes-page-goes-down%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've gone ahead and refactored your application. You have a lot of mistakes that are holding your application back.
Working example: https://codesandbox.io/s/xj553k7nno
Please read the following notes carefully:
- Use the npm package
react-redux(documentation) for connecting and dispatching toredux
- Separate your
containersfrom yourcomponents: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0
- When using
prop-types, I'd recommend definingpropTypesoutside of your class (I prefer it out of theclassorfunctionand before or after theexport). See this for more details. - Create
actionsthat manipulate Redux'sstateand createtypesthat handle whatstateto manipulate. - Common convention for Redux
actionsis toreturnatypeandpayload(although sometimes apayloadmay not be necessary) and for allreducersto expect thattypeandpayloadfrom the action. - Use
switchstatements instead of nestedifandelsestatements for yourreducers. - When
importing please follow this order:
- 1.) Node Modules
- 2.) Components/Containers/Actions/Reducers/Helper functions
- 3.) Stylesheets
- Do not nest invalid HTML elements:
<p><div/></p>(divcan not appear as achildofp) - Do not use vague prop names:
close,open, ...etc. Instead be more declarative:closeModal,openModal, ...etc. - Do not use underscores
_as this is not a common JavaScript naming convention - Reduce repetitive code with reusable components (for example:
ModalColor)! - In this example, React
stateis not needed to update Redux'sstate. Redux can control its ownstatevia theactionsandreducers. - Use
<Fragment></Fragment>or<></>when you need to encapsulate JSX elements that don't need a containing HTML element.
Simplify your application structure:
├── build
| ├── css
| | ├── main.[contenthash:8].css
| | └── main.[contenthash:8].css.map
| ├── js
| | ├── main.[hash].js
| | └── main.[hash].js.map
| ├── media
| | └── [hash].[ext]
| └── favicon.ico
| └── index.html
|
├── public
| ├── favicon.ico
| └── index.html
|
├── src
| ├── actions
| ├── components
| ├── containers
| ├── images
| ├── reducers
| ├── routes
| ├── store
| ├── styles (global)
| ├── tests
| ├── types
| ├── utils
| ├── index.js
| ├── serviceWorker.js
| └── setupTests.js
|
├── .gitignore
├── README.md
├── package.lock.json
└── package.json
add a comment |
I've gone ahead and refactored your application. You have a lot of mistakes that are holding your application back.
Working example: https://codesandbox.io/s/xj553k7nno
Please read the following notes carefully:
- Use the npm package
react-redux(documentation) for connecting and dispatching toredux
- Separate your
containersfrom yourcomponents: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0
- When using
prop-types, I'd recommend definingpropTypesoutside of your class (I prefer it out of theclassorfunctionand before or after theexport). See this for more details. - Create
actionsthat manipulate Redux'sstateand createtypesthat handle whatstateto manipulate. - Common convention for Redux
actionsis toreturnatypeandpayload(although sometimes apayloadmay not be necessary) and for allreducersto expect thattypeandpayloadfrom the action. - Use
switchstatements instead of nestedifandelsestatements for yourreducers. - When
importing please follow this order:
- 1.) Node Modules
- 2.) Components/Containers/Actions/Reducers/Helper functions
- 3.) Stylesheets
- Do not nest invalid HTML elements:
<p><div/></p>(divcan not appear as achildofp) - Do not use vague prop names:
close,open, ...etc. Instead be more declarative:closeModal,openModal, ...etc. - Do not use underscores
_as this is not a common JavaScript naming convention - Reduce repetitive code with reusable components (for example:
ModalColor)! - In this example, React
stateis not needed to update Redux'sstate. Redux can control its ownstatevia theactionsandreducers. - Use
<Fragment></Fragment>or<></>when you need to encapsulate JSX elements that don't need a containing HTML element.
Simplify your application structure:
├── build
| ├── css
| | ├── main.[contenthash:8].css
| | └── main.[contenthash:8].css.map
| ├── js
| | ├── main.[hash].js
| | └── main.[hash].js.map
| ├── media
| | └── [hash].[ext]
| └── favicon.ico
| └── index.html
|
├── public
| ├── favicon.ico
| └── index.html
|
├── src
| ├── actions
| ├── components
| ├── containers
| ├── images
| ├── reducers
| ├── routes
| ├── store
| ├── styles (global)
| ├── tests
| ├── types
| ├── utils
| ├── index.js
| ├── serviceWorker.js
| └── setupTests.js
|
├── .gitignore
├── README.md
├── package.lock.json
└── package.json
add a comment |
I've gone ahead and refactored your application. You have a lot of mistakes that are holding your application back.
Working example: https://codesandbox.io/s/xj553k7nno
Please read the following notes carefully:
- Use the npm package
react-redux(documentation) for connecting and dispatching toredux
- Separate your
containersfrom yourcomponents: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0
- When using
prop-types, I'd recommend definingpropTypesoutside of your class (I prefer it out of theclassorfunctionand before or after theexport). See this for more details. - Create
actionsthat manipulate Redux'sstateand createtypesthat handle whatstateto manipulate. - Common convention for Redux
actionsis toreturnatypeandpayload(although sometimes apayloadmay not be necessary) and for allreducersto expect thattypeandpayloadfrom the action. - Use
switchstatements instead of nestedifandelsestatements for yourreducers. - When
importing please follow this order:
- 1.) Node Modules
- 2.) Components/Containers/Actions/Reducers/Helper functions
- 3.) Stylesheets
- Do not nest invalid HTML elements:
<p><div/></p>(divcan not appear as achildofp) - Do not use vague prop names:
close,open, ...etc. Instead be more declarative:closeModal,openModal, ...etc. - Do not use underscores
_as this is not a common JavaScript naming convention - Reduce repetitive code with reusable components (for example:
ModalColor)! - In this example, React
stateis not needed to update Redux'sstate. Redux can control its ownstatevia theactionsandreducers. - Use
<Fragment></Fragment>or<></>when you need to encapsulate JSX elements that don't need a containing HTML element.
Simplify your application structure:
├── build
| ├── css
| | ├── main.[contenthash:8].css
| | └── main.[contenthash:8].css.map
| ├── js
| | ├── main.[hash].js
| | └── main.[hash].js.map
| ├── media
| | └── [hash].[ext]
| └── favicon.ico
| └── index.html
|
├── public
| ├── favicon.ico
| └── index.html
|
├── src
| ├── actions
| ├── components
| ├── containers
| ├── images
| ├── reducers
| ├── routes
| ├── store
| ├── styles (global)
| ├── tests
| ├── types
| ├── utils
| ├── index.js
| ├── serviceWorker.js
| └── setupTests.js
|
├── .gitignore
├── README.md
├── package.lock.json
└── package.json
I've gone ahead and refactored your application. You have a lot of mistakes that are holding your application back.
Working example: https://codesandbox.io/s/xj553k7nno
Please read the following notes carefully:
- Use the npm package
react-redux(documentation) for connecting and dispatching toredux
- Separate your
containersfrom yourcomponents: https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0
- When using
prop-types, I'd recommend definingpropTypesoutside of your class (I prefer it out of theclassorfunctionand before or after theexport). See this for more details. - Create
actionsthat manipulate Redux'sstateand createtypesthat handle whatstateto manipulate. - Common convention for Redux
actionsis toreturnatypeandpayload(although sometimes apayloadmay not be necessary) and for allreducersto expect thattypeandpayloadfrom the action. - Use
switchstatements instead of nestedifandelsestatements for yourreducers. - When
importing please follow this order:
- 1.) Node Modules
- 2.) Components/Containers/Actions/Reducers/Helper functions
- 3.) Stylesheets
- Do not nest invalid HTML elements:
<p><div/></p>(divcan not appear as achildofp) - Do not use vague prop names:
close,open, ...etc. Instead be more declarative:closeModal,openModal, ...etc. - Do not use underscores
_as this is not a common JavaScript naming convention - Reduce repetitive code with reusable components (for example:
ModalColor)! - In this example, React
stateis not needed to update Redux'sstate. Redux can control its ownstatevia theactionsandreducers. - Use
<Fragment></Fragment>or<></>when you need to encapsulate JSX elements that don't need a containing HTML element.
Simplify your application structure:
├── build
| ├── css
| | ├── main.[contenthash:8].css
| | └── main.[contenthash:8].css.map
| ├── js
| | ├── main.[hash].js
| | └── main.[hash].js.map
| ├── media
| | └── [hash].[ext]
| └── favicon.ico
| └── index.html
|
├── public
| ├── favicon.ico
| └── index.html
|
├── src
| ├── actions
| ├── components
| ├── containers
| ├── images
| ├── reducers
| ├── routes
| ├── store
| ├── styles (global)
| ├── tests
| ├── types
| ├── utils
| ├── index.js
| ├── serviceWorker.js
| └── setupTests.js
|
├── .gitignore
├── README.md
├── package.lock.json
└── package.json
edited Nov 25 '18 at 22:12
answered Nov 25 '18 at 21:25
Matt CarlottaMatt Carlotta
2,8521613
2,8521613
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53470926%2freact-modal-makes-page-goes-down%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown