[tw] [TW5] "SecurityError: The operation is insecure." when trying to save (Firefox on OS X)

2014-07-03 Thread Christian Platzer
When I try to save (either by clicking the download button, or whenever I make an edit while autosave is on), I get the following error message: Internal JavaScript Error Well, this is embarrassing. It is recommended that you restart TiddlyWiki by refreshing your browser SecurityError: The opera

[tw] Re: [TW5] "SecurityError: The operation is insecure." when trying to save (Firefox on OS X)

2014-07-03 Thread Christian Platzer
PS: Below is the console output I receive when going to http://tiddlywiki.com/empty.html and clicking the download button: SecurityError: The operation is insecure. empty.html line 4506 > eval:109 "SecurityError: The operation is insecure." empty.html:4217 Perhaps the line numbers can help narro

[tw] Re: [TW5] "SecurityError: The operation is insecure." when trying to save (Firefox on OS X)

2014-07-04 Thread Christian Platzer
Update: I think I found what's causing the problem for me. It is my cookie settings in Firefox: the error message occurs if the cookie settings are set to never allow cookies - or if they are set to always ask. If I set my cookie settings to allow all cookies, saving tiddly wiki works flawlessl

[tw] Re: [TW5] "SecurityError: The operation is insecure." when trying to save (Firefox on OS X)

2014-07-05 Thread Christian Platzer
Yes, tiddlywiki still works if I disallow 3rd party cookies. But still I would prefer if tiddlywiki was working with all possible cookie settings - or at the very least if it would give a more useful error message in this case ("Please allow cookies" instead of "Internal JavaScript Error") Am F

Re: [tw] Re: [TW5] "SecurityError: The operation is insecure." when trying to save (Firefox on OS X)

2014-07-05 Thread Christian Platzer
Hi Jeremy, even with a brand new Firefox profile (which should be perfectly blank, without any addons or plugins), the error occurs as soon as I change the cookie settings. I can also reproduce the same problem on my second computer (Window 8 32bit), so it seems to be independent of the operati