Whenever I am trying to test play my own 1.42 stories. The alert pops up on the first page. Then the back button stops working. I checked and it happened to twine game developed by other too. Did chrome change their security or something? Anyone know? How can an author check the player browser and take care of it, or at least warn the user with a solution?
I think this happens after a chrome update.
The problem does not exist in opera
I know i am asking a chrome question in the twine forum but, hey, I think some authors may want to know this too.
2) I want a floating div (absolute position div) on top of the passage, loading from the sidebar. however no matter how high z-index is set the passage is always on top of the floating div. I have even try setting the passage z-index to 5 and my floating div to 1500 and still the passage sit on top of my div. Any idea why? It happens both on chrome and opera.
so what can I do? I use sugercane.
The workaround set the passage to display none when my pops up load, skipping the z-index mess all along.
1. Use a different brand browser to view your story(s).
Maybe you will be able to change back to Chrome if Google changes their mind again.
2. Change to the SugarCube story format, which has been patched to stop this error.
It supports all the Sugacane macros, although you will need to check and update your CSS because SugarCube uses some different base CSS selectors.
3. Run an instance of Chrome with the --allow-file-access-from-files parameter.
WARNING: This partially changes Chrome's security model so don't use this instance to assess the internet.
4. Wait until the developer (or someone else) or Sugarcane patches it.
This maybe a long wait because it requires a new release of Twine 1.x, and even though the source code of Twine 1.x (and it's story formats) have been update as recently as June 2015 there has not been a release of Twine 1.x for more than a year.
An example of your existing CSS would help, so whoever tries to solve this issue knows exactly what you have modified.
Does it means that it is a forced switch to twine version 2? As far as I can tell, the markup language is not backward compatible, not to mention all the scripts.
Both SugarCube 1 and 2 have been patched to handle this issue better.
The markup language is determined by which Story Format you use, not which version of Twine.
I have installed and tried switching over to sugarcube on my current game and I am still having error. It said something about having me putting the page on somewhere so that I can access it through http... well, not a solution I am expecting.
I have been using sugarcane all these years. Does it means that I can use sugarcane when I move over to twine 2? I remember trying out twine when it first launch and that option is not available.... but then not even the offline version was available.
That is a notification that your browser lacks required capabilities, not an error. It's what any conscientious story format should be doing in the unenviable position where the browser is either so old as to simply lack the required features or, in this case, the browser is actively and willfully sabotaging locally opened web applications.
No. Sugarcane is Twine 1 only.
I can't port to twine 2 because I use macros that I don't know how to rewrite for twine 2.
Anyway, this sucks enormously.
What does Twine 2 have to do with anything? The issue in question affects story formats, not the IDE/compiler you happen to be using.
Anyway. If you want a story format which is completely immune to the Chromium issue, then you basically have two choices: