OpenCloud
/
riot-web
mirror of https://github.com/vector-im/riot-web
1
0
Fork 0
Code Issues Releases Wiki Activity

Fix device verification from e2e info 

Don't attempt to reuse the same AsyncWrapper for different dialogs - which ends
up pushing the props for the new dialog into the old dialog.

Fixes https://github.com/vector-im/riot-web/issues/3020
pull/21833/head
Richard van der Hoff 2017-01-23 12:18:41 +00:00
parent 937f13d578
commit dc08d9dfdf
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/Modal.js
View File

@ -67,6 +67,8 @@ const AsyncWrapper = React.createClass({
},
});
let _counter = 0;
module.exports = {
DialogContainerId: "mx_Dialog_Container",
@ -113,12 +115,16 @@ module.exports = {
ReactDOM.unmountComponentAtNode(self.getOrCreateContainer());
};
// don't attempt to reuse the same AsyncWrapper for different dialogs,
// otherwise we'll get confused.
const modalCount = _counter++;
// FIXME: If a dialog uses getDefaultProps it clobbers the onFinished
// property set here so you can't close the dialog from a button click!
var dialog = (
<div className={"mx_Dialog_wrapper " + className}>
<div className="mx_Dialog">
<AsyncWrapper loader={loader} {...props} onFinished={closeDialog}/>
<AsyncWrapper key={modalCount} loader={loader} {...props} onFinished={closeDialog}/>
</div>
<div className="mx_Dialog_background" onClick={ closeDialog.bind(this, false) }></div>
</div>