Problem with exporting a Squiffy story into HTML and Javascript

I download a Squiffy story by exporting it into HTML and Javascript. Then, I unzip the zip archive into its own folder. Finally, I open index.html in either Google Chrome (Windows 10).

Nothing appears on the page, just the Restart link at the top right.

I can make the content show in Internet Explorer 11 by allowing blocked content. To do the same in Chrome, I have to not block third party cookies and site data. And I just don't want to do that.

This may be a really dum question, but apart from I creating an exception for each Squiffy program that I wish to display in Chrome, is there a way to keep blocking third party cookies and site data and have Squiffy HTML/Javascript downloads show properly in Chrome?


You could comment out all references to the save function in the story.js file. There's about four references. You obviously won't be able to save your progress if you do this.

Basically by default squiffy tries to load from local storage on startup, and saves today local storage after every user action. By removing these calls from the story.js file this will never occur and you won't run into the blank screen issue.

Aside from that I can't think of any workaround, except allowing local data storage.


Thanks for explaining.

In my opinion, Squiffy has to find a way to work with this restriction.

It appears that there are security concerns with third party cookies, e.g. http://www.macworld.com/article/3106793/security/disable-third-party-cookies-as-a-hedge-against-a-new-browser-based-attack.html.

Also, and perhaps more importantly, certain browsers, such as the Microsoft Edge (Windows 10), cannot be made to work with Squiffy HTML/Javascript downloads even if all related security options have been cleared. No matter what I do with the setting in Edge, Squiffy HMTL/Javascript downloads still look blank in Microsoft Edge.

So, for the moment, I will keep blocking third party cookies and site data and will rely on running Squiffy online.


Hmm, I use Edge all the time and have never had any issue with Squiffy.

The main known issue is that some browsers, in private browsing mode, will disable access to local storage. But the workaround is to simply revert to normal browsing.

To be fair, I'm not sure what sort of workaround would be possible if you don't want to allow any access to your computer. Cookies are probably the safest option from a security point of view.

I guess you could implement some sort of server side saving mechanism, storing it on the server rather than local PC, but then you'd not be able to play games offline.

I did suggest some code to the main Squiffy developer that basically ran an initial check for access to local storage and, if not available, would throw up an explanation as to why the game would not run.

It would be pretty easy to develop this further so that, in the event of no access, the game disables the save system and tells the player that they will be unable to save.

For example, if you pop the code below into your index.html file it will show a pop-up if access to local storage is disabled.

<script>
try { localStorage.test = 2; } catch (e) {
alert("my error message");
}
</script>

No problems with Edge? May I know about your precise settings please?

In my case, in Edge settings --> View Advanced Settings, I have:

Show home button = ON
Block pop-ups = ON (might this cause a problem?)
Use Adobe flash player = ON
Open sites in apps = ON
Ask me what to do with each download = ON (should not matter)
Offer to save passwords = on
Save form entries = on
Send do not track requests = OFF
Have Cortana assist me = OFF
Don't block cookies
Let sites save protected ... = ON
Use page prediction ... = ON
Help protect me from malicious sites = OFF

Is there a problem with these settings?

Might there be a problem with my Internet settings (from Control Panel)?

I would love to have Edge display my downloaded Squiffy HTML/Javascript stories, because I would then easily use them in class!


This topic is now closed. Topics are closed after 60 days of inactivity.

Support

Forums