Maciej Sopyło

I think this issue is no longer tracked in the linked taiga ticket? The taiga one is closed and the only thing from this one that's implemented are overlays. Transitions/animations...

Looks simple enough, is there a documentation somewhere? Also which carrier is that?

> that spec ? ^ Exactly, I guess I didn't know what to look for. I guess a partial implementation would be displaying these nicely / in the correct conversation...

Same on Pixel 2XL, can be reliably reproduced. Log from one crash to another - here it died at 4 apps left since I had more: https://pastebin.ubuntu.com/p/ky4vvGDrNF/

Hmm, my reasoning for the dialog was that ContentHub at the moment is just a QML component that's included in the app and the app has total control over it...

> I understand your reasoning, but don't webapps use qml anyway? (like the overlay for external url?), and you have to provide a Dialog qml anyway. And the ContentHub has...

@cibersheep created a flow for ContentHub-style selection and I have to agree, it doesn't look out of place :D [Flow 3: ContentHub-style app selection](https://design.penpot.app/#/view/da3375b0-195a-11ed-817f-f940e3befd53?page-id=da3375b1-195a-11ed-817f-f940e3befd53&section=interactions&index=7&share-id=6f2149f0-1964-11ed-817f-f940e3befd53)

@cody271 did you start working on this? I need this feature and want to make it, but if you started already I don't want to reinvent the wheel ;)

@DemiMarie then only allow local content? Adding ~50MB to the lib just for the sandbox is unacceptable. Restrict to local content by default and if someone wants to disable that...

My use case was a widget that would display a React/Angular/Vue/etc component you are working on in isolation with ability to tweak the props. I'd really not worry about sandboxing...