Followed up with Nick Reynolds via slack. Here's their use case and why we should support it: @masoudahg00 @masoudleyli

[masoudahg00]

          Followed up with Nick Reynolds via slack. Here's their use case and why we should support it:

so there's 2 reasons for our dapp requiring web3 in iframes
kirby: our dapp connects web3 wallets using a framework known as kirby (https://blog.joincivil.com/kirby-and-the-birth-of-wall-apps-bd6ce396e229) . Kirby works by sending messages from a parent app to a child app using postMessage, and the child iframe needs web3 injected in order to connect to MetaMask.
embedded components: we're building components for microtipping that newsrooms will embed via iframes in their articles. these embedded components need web3
for context, it appears that Coinbase Wallet injects web3 into iframes (haven't quite gotten it to work, actually, but the iframe is aware of Coinbase Wallet's web3). And of course, this flow works on desktop with MetaMask extension since that injects web3 into iframes.
this is all in service of our goal to build tools for publishers that have no experience in this area. using iframes provides a much quicker time to market than directly integrating with their application

Originally posted by @brunobar79 in MetaMask/metamask-mobile#1154 (comment)
@masoudahg00 @Masoudleyli