HyperSwitch's SDK / links is meant to work within top context at the client side. This behaviour changes when we introduce secure links - which are supposed to be iframed within merchant's top context. Any functionality which was consuming top context at the client side needs to be handled accordingly.
Possible Implementation
Major things which needs to be handled
client side redirections to happen at top context
client side redirections happen within current window context - which is assumed to be top (since the SDK integration requires this to be at top level)
when using iframed resources, SDK should handle redirection and make sure this happens in the top context
accessing protocol and hostname
this is also fetched from within the current window's context
needs to happen at top context
Have you spent some time checking if this feature request has been raised before?
kashif-m
commented
1 week ago
Feature Description
HyperSwitch's SDK / links is meant to work within top context at the client side. This behaviour changes when we introduce secure links - which are supposed to be iframed within merchant's top context. Any functionality which was consuming top context at the client side needs to be handled accordingly.
Possible Implementation
Major things which needs to be handled
protocolandhostnameHave you spent some time checking if this feature request has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!