WOOT TEH??

[iDrugoy]

I've hit "CTRL+Z" while I was editing ABE rules AND THEY ALL HAVE GONE!
Huh? How to restore them?

[Thrawn]

Ctrl-Z generally means 'Undo', so I don't see why it would clear your ABE rules, unless you had just copied a block of text over the top of them.

If you have backups of your Firefox profile, you can look there; otherwise, you're probably out of luck.

[GµårÐïåñ]

Well Ctrl+Z is undo and Ctrl+Y is redo, so try that but if you have closed the window, its gone.

[iDrugoy]

I didn't paste my rules as a text from clipboard, I've saved them earlier. But they all are gone.
The thing is that CTRL+Z messes up with "SYSTEM" and "USER" ABE rulesets. I had one of them completely clear (and maybe even disabled), then I hit CTRL+Z in the other one and everything there has gone.

[iDrugoy]

+ Ctrl+Z should remember the history of the corrections only since the moment NoScript's settings window was opened, but you may test it yourself - it remembers more!

[Thrawn]

You know what? You're right. Ctrl+Z clears all. Ctrl+Y restores. Perhaps when you open the dialog, NoScript is pasting in the text of your ABE rules, and this is treated as a normal insertion that you can undo.

I'd have to think that this is an undesirable side effect of how the ABE rules entry field is being managed. If Giorgio gets a chance, and there's an easy way to fix it, that's probably worth doing.

In the meantime: use caution when editing rules, and if something goes horribly wrong, then use Cancel instead of OK!

[GµårÐïåñ]

I understand that Ctrl+Z holds more than one action, that's why I suggested using Ctrl+Y to restore it while you are still in the dialog, a sentiment therube has echoed as well. If you at any point dismissed the active dialog however, yes you will lose it permanently. I don't remember this being an issue and I am not facing it, perhaps a system configuration issue. Perhaps a clipboard hook or something that is connected in such a manner to clipboard to affect its behavior. Such as Klipper on Linux, Ditto on Windows and many others.

[barbaz]

if something goes horribly wrong, then use Cancel instead of OK!

To note, clicking Cancel won't discard changes to ABE rules, and that isn't a bug.

[iDrugoy]

if something goes horribly wrong, then use Cancel instead of OK!

To note, clicking Cancel won't discard changes to ABE rules, and that isn't a bug.

Yeah, these guys are ridiculous. They can explain any bug as 'not-a-bug-but-cool-feature'.

[Thrawn]

Not a cool feature, but a limitation of the current architecture. Giorgio hasn't actually made a mistake in how he has written it, but the current behavior has undesirable effects. He would have to redesign that part of the GUI to change it.

[barbaz]

Not a cool feature, but a limitation of the current architecture.

Erm, GµårÐïåñ said it's actually intentional/deliberate/by design: viewtopic.php?p=70460#p70460