-
Notifications
You must be signed in to change notification settings - Fork 68
Use Case: 3rd Party Content for Secure Sites #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the feedback! Yes, this is one of the main use cases we have considered since the start of the design. Basically, we want to be able to provide a user experience where the user transitions from a page, to a payment processor, back to the page, with smooth transitions, but at the same time being able to verify the origin of the payment processor through the URL bar, which isn't possible with iframes. |
@ChadKillingsworth Your use case is to use portals to transition users away from your platform? |
Yes. Imagine a portal embedded in your online banking site that shows investment accounts at a brokerage. Or invoices and payments from a small business budget site. Interaction with these sites would indeed take you away from my platform. This allows a financial institution to partner with another provider and provide rich interactive launch points within my platform. |
History / Back button support would be important for us. The version of portals in Chrome Canary doesn't seem to work with the back button. I'm not sure that's intentional though. |
@ChadKillingsworth This is a known issue and it's tracked on #19 . |
I just wanted to document my use case and re-enforce the utility that portals would bring.
I develop an online banking platform for hundreds of US based financial institutions. We're planning on allowing 3rd parties to provide rich web apps embedded in our site via sandboxed iframes. However navigation will take the user to the 3rd party site. After seeing portals, it seems like a much better experience and highly preferable to a standard iframe.
Since this is outside of the standard link aggregation site use case, I wanted to re-enforce the utility in other types of sites.
The text was updated successfully, but these errors were encountered: