Mark Stacey 63bd422840 Handle one specific permissions request per tab (#7620) ... The connect route now takes a route parameter: the permissions request id. This id is set whenever the permissions connect screen is opened, ensuring that that tab is for that specific request alone. This makes handling of multiple permissions requests a bit more intuitive. Previously whenever opening multiple permissions requests, the first one would be shown on each successive tab, whereas you would expect each tab to show the request that prompted the tab to open. Users may now address permissions request in whichever order they'd like to, rather than being forced to deal with them chronologically.		2019-12-05 17:05:50 -04:00
..
choose-account	Connect distinct accounts per site (#7004)	2019-12-03 09:35:56 -08:00
permissions-connect-footer	Connect distinct accounts per site (#7004)	2019-12-03 09:35:56 -08:00
permissions-connect-header	Fix the permissions connect screen MetaMask logo (#7641)	2019-12-04 19:57:30 -04:00
index.js	Connect distinct accounts per site (#7004)	2019-12-03 09:35:56 -08:00
index.scss	Connect distinct accounts per site (#7004)	2019-12-03 09:35:56 -08:00
permissions-connect.component.js	Handle one specific permissions request per tab (#7620)	2019-12-05 17:05:50 -04:00
permissions-connect.container.js	Handle one specific permissions request per tab (#7620)	2019-12-05 17:05:50 -04:00