You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you look at how jsfiddle, jsbin et al. works they all have <iframe> for sandboxing rendered content. We don't have it, just render things in a <div> and then it causes unexpected behaviors, like <BODY> referencing the body of the whole application, not the body of the instant's viewport.
When you look at how jsfiddle, jsbin et al. works they all have
<iframe>
for sandboxing rendered content. We don't have it, just render things in a<div>
and then it causes unexpected behaviors, like<BODY>
referencing the body of the whole application, not the body of the instant's viewport.Take a look at this sample
http://instant.ariatemplates.com/anonymous/656ad51fd658295887d8/3e1f96
it's just a copy-paste of a usermanual entry
http://ariatemplates.com/usermanual/next/processingindicator
Since BODY is the IA app, the "whole" page overlay behaves quite unexpectedly.
The text was updated successfully, but these errors were encountered: