Keeping ZAFClient state across iframe reloads (feature request)
Hello all,
We are developing a zendesk app that is loaded inside an iframe. ZAFClient is correctly initialized on the first request but the state (app_guuid, origin) is not persisted between full reloads of the iframe, as a result the reloaded iframe cannot initialize a ZAFClient instance.
There are a few workarounds to that, most of them a bit hackish or difficult to implement (e.g. using a SPA that holds the state).
We were thinking of another solution, what if Zendesk exposed an additional postMessage API (e.g. by responding to a 'getZAFParameters' message) that returned the app_guid & origin. It seems simple & clean, the parent Zendesk window has the full state and knows the app_guid since it created the iframe in the first place.
Would that sound like a reasonable addition?
ps: we are currently experimenting with a double iframe solution, where the wrapper iframe keeps app_guid and proxies message between Zendesk and the inner application iframe, but we don't quite like the added complexity of that solution.
-
Hi Christos,
On reload of the iframe, a new instance of ZAFClient needs to be initialized - resulting in a new app_guid value. Can you provide some more context about the app (including relevant sample code if helpful) that demonstrates where you're having trouble initializing ZAFClient?
Thanks,
댓글을 남기려면 로그인하세요.
1 댓글