All looks good! Re-enabling permissions per TW file isn't really bad, though if I may add a small request on this front: It would be awesome if there was someway to prevent being asked for permission for permalinks.
Where as currently and for as long as I've been using TiddlyFire I have to allow permissions once for every unique set of permalinks: empty.html#MakingLists empty.html#MarkUp empty.html#jQuery empty.html#GettingStarted empty.html#MakingLists MarkUp empty.html#MakingLists MarkUp jQuery empty.html#MakingLists MarkUp jQuery GettingStarted empty.html#MarkUp jQuery empty.html#MarkUp jQuery GettingStarted empty.html#jQuery GettingStarted At this point for my main tiddler wiki has probably accumulates well into the hundreds if not close to a thousand permission grants due to my extensive use of permalinks. Of course at this point I'm use to clicking hitting okay so often when refreshing and opening temp links It could though of my rythem if that was changed. XD On Tuesday, April 23, 2013 2:06:37 PM UTC-7, Jeremy Ruston wrote: > > Hi Arc > > Thanks, I've uploaded a new version which should fix that extraneous alert. > > As things stand, users will have to re-enable permissions for each TW that > they use at the point that they upgrade Firefox to version 23. I'll have a > think about strategies for avoiding that. > > Best wishes > > Jeremy. > > > On Tue, Apr 23, 2013 at 9:20 PM, Arc Acorn <[email protected]<javascript:> > > wrote: > >> Firefox 18,19,20,21,22,23 : >> On every load/start this window shows up: >> >> >> <https://lh3.googleusercontent.com/-RWnY21JJlc4/UXbqED78A2I/AAAAAAAAAHw/mdBW2pECnCE/s1600/2013-04-23_130731.png> >> >> Outside of that everything seems to be working like normal. Wikis can >> save/export/make backups and the normal permission box only shows it's self >> on the first load. >> >> >> On Tuesday, April 23, 2013 3:18:30 AM UTC-7, Jeremy Ruston wrote: >> >>> Hi Arc >>> >>> I've gone ahead and created a new further 1.0alpha14 that uses local >>> storage in older versions of Firefox. I'd be grateful if you could give it >>> a go and see how you get on, >>> >>> Many thanks, >>> >>> Jeremy >>> >>> >>> On Mon, Apr 22, 2013 at 8:32 PM, Jeremy Ruston <[email protected]>wrote: >>> >>>> Hi Arc >>>> >>>> Thanks once again for your sleuthing. It turns out that the problem is >>>> a bug in Mozilla that prevents the preferences API from working correctly >>>> on documents loaded from a file URI. Here's the bug: >>>> >>>> https://bugzilla.mozilla.org/**show_bug.cgi?id=204285<https://bugzilla.mozilla.org/show_bug.cgi?id=204285> >>>> >>>> It appears it was fixed in Firefox 21, which lines up with your tests. >>>> >>>> So, frustratingly the current position is: >>>> >>>> * We have localstorage-based code that works in Firefox up to and >>>> including version 22 >>>> * We have nsIPermissionManager-based code that works in Firefox version >>>> 21 and up >>>> * The addons.mozilla.org editors require TiddlyFox not to use >>>> localstorage in order for new versions to go back in the catalogue >>>> >>>> The obvious answer is to carry the code for both mechanisms, and switch >>>> according to availability. I'm not sure how that strategy will play with >>>> the AMO editors, though. >>>> >>>> I'll continue investigations and report back, >>>> >>>> Best wishes >>>> >>>> Jeremy >>>> >>>> >>>> >>>> On Mon, Apr 22, 2013 at 7:42 PM, Arc Acorn <[email protected]> wrote: >>>> >>>>> Seems to be working great for 23.0a1, 22.0a2, & 21 >>>>> Tested on 32x & 64x Windows builds. >>>>> >>>>> It dose however seam to break support for older Firefox builds: Not >>>>> working on Windows 32x builds for 20,19, &18 (probably more I just have >>>>> these 3 handy). >>>>> >>>>> >>>>> On Monday, April 22, 2013 8:53:23 AM UTC-7, Jeremy Ruston wrote: >>>>> >>>>>> Hi Arc >>>>>> >>>>>> It turns out that 23 disables access to local storage from >>>>>> extensions, which is how TiddlyFox has been storing it's preferences. >>>>>> >>>>>> I've updated TiddlyFox to use the recommended permission API, and it >>>>>> seems to work for me with 23.0a1. It doesn't attempt to transfer any >>>>>> permissions already in local storage, so you will have to re-approve >>>>>> each >>>>>> file that you use. >>>>>> >>>>>> Download the new version from: >>>>>> >>>>>> https://github.com/TiddlyWiki/****TiddlyFox/raw/master/**tiddlyfox** >>>>>> .xpi<https://github.com/TiddlyWiki/TiddlyFox/raw/master/tiddlyfox.xpi> >>>>>> >>>>>> If it looks like it's working I'll submit it to the Mozilla Add-ons >>>>>> site, which will cause it to be autoupdated for most people. >>>>>> >>>>>> Best wishes >>>>>> >>>>>> Jeremy >>>>>> >>>>>> >>>>>> On Mon, Apr 22, 2013 at 9:46 AM, Jeremy Ruston >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Thanks Arc, I've downloaded Firefox 23.0a1 on OS X and I'm >>>>>>> experiencing the same behaviour. I'll investigate further and post back >>>>>>> here, >>>>>>> >>>>>>> Best wishes >>>>>>> >>>>>>> Jeremy >>>>>>> >>>>>>> >>>>>>> On Mon, Apr 22, 2013 at 8:22 AM, Arc Acorn <[email protected]>wrote: >>>>>>> >>>>>>>> I realize things having to do with nightly builds are always a bit >>>>>>>> iffy, but I figure'd I would report that TiddlyFox is no longer >>>>>>>> working as >>>>>>>> of the Firefox 23.0a1 >>>>>>>> >>>>>>>> When trying to save I get the generic "not possible to save >>>>>>>> changes" notice. >>>>>>>> >>>>>>>> >>>>>>>> On Tuesday, March 19, 2013 2:45:44 PM UTC-7, Yakov wrote: >>>>>>>>> >>>>>>>>> Hi Jeremy and Arc, >>>>>>>>> >>>>>>>>> today I encountered one more corruption, of a big TW (took hell of >>>>>>>>> time to recover), so today is the time to dig this more. >>>>>>>>> >>>>>>>>> First, the online services. Well, they can be easily found by >>>>>>>>> googling smth like "decode text online".. well, I've done this in >>>>>>>>> russian >>>>>>>>> and hence used russian services, but to give an example, I'll say >>>>>>>>> that the >>>>>>>>> one which worked well is [1]. It is quite straight-forward, the first >>>>>>>>> button under the text area is "fit the encoding", the next one is to >>>>>>>>> be >>>>>>>>> used if you know how the text is actually encoded, the third one is >>>>>>>>> "decode >>>>>>>>> as previously" and the forth line contains examples of what you would >>>>>>>>> get >>>>>>>>> if you decode with another encoding pair (the buttons sais "show"). >>>>>>>>> It is a >>>>>>>>> little bit slow at times, but has a better "toolkit" which allows to >>>>>>>>> decode >>>>>>>>> anyway. Two more notes: if one tries to decode a whole tiddler, he or >>>>>>>>> she >>>>>>>>> should be aware that in the resulting text he'll get "<>" instead of >>>>>>>>> each >>>>>>>>> instance of macro ("<<...>>"); and that for multiline content it's >>>>>>>>> necessary to track extra spacebars in the ends of lines (which appear >>>>>>>>> and >>>>>>>>> which can break tables etc). >>>>>>>>> >>>>>>>>> Second, I've redone the testing (with the files attached >>>>>>>>> previously). I found that my TF version was 1.0alpha10. The same >>>>>>>>> tests with >>>>>>>>> TW 1.0alpha12 showed no bug. I'll test with other TWs later and >>>>>>>>> report if >>>>>>>>> any problem remained. >>>>>>>>> >>>>>>>>> As for the "Error when including 'zz microrep commons.html':" >>>>>>>>> message, it's ok, it sais that the TiddlyWiki that is included by >>>>>>>>> <<include>> macro is not actually present. >>>>>>>>> >>>>>>>>> "TypeError: a.fetchTiddler is not a function" is a more serious >>>>>>>>> issue, I got this bug once or twice in FF but can't reproduce it >>>>>>>>> (aside in >>>>>>>>> FF for Android, where I don't have many tools for debugging). Further >>>>>>>>> details about this bug are welcome in the STP thread [2]. >>>>>>>>> >>>>>>>>> I forgot to test a TW without STP before updating TF, so can't >>>>>>>>> really be sure what is the source of the encoding problem. STP >>>>>>>>> doesn't >>>>>>>>> really do anything with encodings and with the saving procedure as a >>>>>>>>> whole, >>>>>>>>> so I wouldn't expect it to be the source of the problem.. but in >>>>>>>>> principle >>>>>>>>> it can drive some bugs in other engines (TF itself or some more >>>>>>>>> complicated >>>>>>>>> chain). >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> http://www.online-decoder.com/******ru<http://www.online-decoder.com/ru> >>>>>>>>> [2] https://groups.google.com/**foru****m/?fromgroups=#!topic/** >>>>>>>>> tiddlywi****ki/rQz8aDt76vQ<https://groups.google.com/forum/?fromgroups=#!topic/tiddlywiki/rQz8aDt76vQ> >>>>>>>>> >>>>>>>>> пятница, 15 марта 2013 г., 17:47:50 UTC+4 пользователь Jeremy >>>>>>>>> Ruston написал: >>>>>>>>>> >>>>>>>>>> Hi Yakov >>>>>>>>>> >>>>>>>>>> Sorry you've been having problems, but delighted you've been able >>>>>>>>>> to save your work. It might be useful for others if you could share >>>>>>>>>> your >>>>>>>>>> experiences of using the online services that you mentioned. >>>>>>>>>> >>>>>>>>>> I'm having trouble with the file "fet mr copy for brutal test - >>>>>>>>>> before.html". When it first opens, I get the message "Error when >>>>>>>>>> including >>>>>>>>>> 'zz microrep commons.html':", and then many macros failing with the >>>>>>>>>> error >>>>>>>>>> "TypeError: a.fetchTiddler is not a function". I assume this is the >>>>>>>>>> problem >>>>>>>>>> with the SharedTiddlersPlugin that Arc reports. Can you share a >>>>>>>>>> version of >>>>>>>>>> the file that doesn't use STP? >>>>>>>>>> >>>>>>>>>> Many thanks >>>>>>>>>> >>>>>>>>>> Jeremy >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Mar 15, 2013 at 9:00 AM, Arc Acorn <[email protected]>wrote: >>>>>>>>>> >>>>>>>>>>> My test setup: TiddlyFox 1.0Alpha11 + FireFox 19 on Windows 7 >>>>>>>>>>> x64 (sp0) >>>>>>>>>>> Using the linked: "fet mr copy for brutal test - before.html" >>>>>>>>>>> file. >>>>>>>>>>> >>>>>>>>>>> I had to manual delete the "SharedTiddlersPlugin" before it >>>>>>>>>>> would let me make edits, however after that I had no issues making >>>>>>>>>>> edits >>>>>>>>>>> and saving with all the non-Latin characters staying intact. >>>>>>>>>>> >>>>>>>>>>> You may try uninstalling TiddlyFox and downloading a fresh copy: >>>>>>>>>>> https://github.com/TiddlyWiki/******TiddlyFox<https://github.com/TiddlyWiki/TiddlyFox> >>>>>>>>>>> Maybe some how or another you got the older version that had >>>>>>>>>>> issues of this nature. >>>>>>>>>>> >>>>>>>>>>> Even though I had no issues using/saving this TiddlyWiki (2.6.5) >>>>>>>>>>> you may still consider updating to 2.7.1: >>>>>>>>>>> https://groups.google.com/**foru****m/#!topic/tiddlywiki/** >>>>>>>>>>> x2aBkaFn5****A0<https://groups.google.com/forum/#!topic/tiddlywiki/x2aBkaFn5A0> >>>>>>>>>>> To see if it helps fix your problem, as issues of >>>>>>>>>>> a similar nature are listed as the major reason for the update. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thursday, March 14, 2013 4:56:23 PM UTC-7, Yakov wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi Chris, >>>>>>>>>>>> >>>>>>>>>>>> I'm afraid I'm not that familiar with the technical details (of >>>>>>>>>>>> the saving process) to understand what do you mean. >>>>>>>>>>>> >>>>>>>>>>>> This test causes corruption of the whole non-latin content, not >>>>>>>>>>>> just of the part which was edited, so I don't understand what do >>>>>>>>>>>> you mean by >>>>>>>>>>>> >>>>>>>>>>>> > treating all content as UTF-8 encoded and _nothing_ else and >>>>>>>>>>>> don't bother to check before decoding or encoding what encoding >>>>>>>>>>>> might >>>>>>>>>>>> already be present >>>>>>>>>>>> >>>>>>>>>>>> The stored (non-edited) content should probably be in UTF-8 as >>>>>>>>>>>> TW edited it with its own engines, shouldn't it? >>>>>>>>>>>> >>>>>>>>>>>> Best regards, >>>>>>>>>>>> Yakov. >>>>>>>>>>>> >>>>>>>>>>>> четверг, 14 марта 2013 г., 15:42:59 UTC+4 пользователь Chris >>>>>>>>>>>> Dent написал: >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, 13 Mar 2013, Yakov wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> > Hi Jeremy, >>>>>>>>>>>>> > >>>>>>>>>>>>> > I think I have bad news. Today I edited couple of my TWs >>>>>>>>>>>>> (fortunately minor >>>>>>>>>>>>> > ones) via FF (with TiddlyFox) and they got badly corrupted. >>>>>>>>>>>>> Those wikis >>>>>>>>>>>>> > contain text in cyrillics, and seem to be wrongly encoded. >>>>>>>>>>>>> Auto-decoding >>>>>>>>>>>>> > via some online survice shows that the encoding is partially >>>>>>>>>>>>> CP1163, >>>>>>>>>>>>> > partially ISO-8859-1 (and sometimes even that is not 100% >>>>>>>>>>>>> correct). >>>>>>>>>>>>> > Fortunately, I've restored everything via decoding. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Not Jeremy, but I have a guess about what's going on. I would >>>>>>>>>>>>> guess >>>>>>>>>>>>> that both TiddlyWiki and TiddlyFox are predisposed to treating >>>>>>>>>>>>> all >>>>>>>>>>>>> content as UTF-8 encoded and _nothing_ else and don't bother >>>>>>>>>>>>> to >>>>>>>>>>>>> check before decoding or encoding what encoding might already >>>>>>>>>>>>> be >>>>>>>>>>>>> present. >>>>>>>>>>>>> >>>>>>>>>>>>> TiddlyWeb certainly takes this tactic. It minimizes complexity >>>>>>>>>>>>> while >>>>>>>>>>>>> maximizing possible character representations. >>>>>>>>>>>>> -- >>>>>>>>>>>>> Chris Dent >>>>>>>>>>>>> http://burningchrome.com/ >>>>>>>>>>>>> [...] >>>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>> Google Groups "TiddlyWikiDev" group. >>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>> it, send an email to tiddlywikide...@googlegroups.**c****om. >>>>>>>>>>> To post to this group, send email to [email protected]. >>>>>>>>>>> Visit this group at http://groups.google.com/**group**** >>>>>>>>>>> /tiddlywikidev?hl=en<http://groups.google.com/group/tiddlywikidev?hl=en> >>>>>>>>>>> . >>>>>>>>>>> For more options, visit https://groups.google.com/**grou**** >>>>>>>>>>> ps/opt_out <https://groups.google.com/groups/opt_out>. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Jeremy Ruston >>>>>>>>>> mailto:[email protected] >>>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Jeremy Ruston >>>>>>> mailto:[email protected] >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Jeremy Ruston >>>>>> mailto:[email protected] >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Jeremy Ruston >>>> mailto:[email protected] >>>> >>> >>> >>> >>> -- >>> Jeremy Ruston >>> mailto:[email protected] >>> >> > > > -- > Jeremy Ruston > mailto:[email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
