Bug 14219
Summary: | TiddlyWiki saving doesn't work | ||
---|---|---|---|
Product: | WebKit | Reporter: | Tommi Komulainen <tkomulai+webkit> |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | ap |
Priority: | P2 | ||
Version: | 523.x (Safari 3) | ||
Hardware: | Mac | ||
OS: | OS X 10.4 | ||
URL: | http://tiddlywiki.com/ |
Tommi Komulainen
With webkit nightlies TiddlyWiki and derivatives are unable to save any changes to local files, all attempts just show a "It's not possible to save changes." error dialog with varying verbosity.
I've tried both the java (http://tiddlywiki.com/#TiddlySaver) and plugin (http://www.dcs.gla.ac.uk/~jp/tiddlywiki/) workarounds and neither one is working with webkit nightlies. Both seem to be working with Safari2.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
If confirmed, this would be a P1 bug.
Could you please provide detailed steps to reproduce (as in "open this site, click this particular link, type this text, expect that behavior")?
Tommi Komulainen
1. Download http://tiddlywiki.com/empty.html
2. Open the local file
3. Click 'save changes' in the sidebar on the right
Alexey Proskuryakov
After following these steps in Safari 2, all I got was an error message saying "It's not possible to save changes."
Doing the same in Firefox, I got a request for additional privileges from the script, which I didn't grant, not knowing what they were needed for.
Alexey Proskuryakov
The Java workaround was verified to work correctly with TOT (works for me, and confirmed by the reporter on IRC):
1) Create a folder ~/Documents/tiddlywiki-folder
2) Create a .java.policy file, as described at http://tiddlywiki.com/#TiddlySaver
3) Save http://tiddlywiki.com/empty.html to tiddlywiki-folder
4) Open it
5) Click 'save changes' in the sidebar on the right
A new saved file appears in tiddlywiki-folder.
I don't think this is supposed to work without a Java applet or plugin in WebKit, because scripts cannot request elevated privileges, as TiddlyWiki does in Firefox code path. In the future, HTML5 persistent storage may provide a better foundation for such applications.