Zapper: Add "undo" button along with "close" button

[jocelynetienne]

It happens when using Zapper that one zaps out some useful content by mistake. Now that there's a "close" button for zapper, it seems very doable to add also an "↩ Undo" button.

[u-RraaLL]

1. Not possible. How do you want uBO to restore something you've just deleted from your browser?
2. Refresh the page. Zapper is a temporary tool for the current page load only.

[gorhill]

It is possible for the zapper to keep a reference on the removed element and its parent so that it could be put back. I feel it might be a good feature to be able to undo the last removal at least rather than have to reload the page.

[stephenhawk8054]

It is possible for the zapper to keep a reference on the removed element and its parent so that it could be put back.

If I'm not wrong, removing the node will also remove the events attached to that node? If so, would putting it back restore those events as well?

[gorhill]

It wouldn't restore event handlers if any, but I still think it might be useful, especially for Android, it's easier to mistakenly remove something.

[krystian3w]

Does restoring a DOM from Dev Tools also remove listening events?

Maybe it's possible to pretend that the DOM is being deleted as if from a closed dev tools level - Profitable when most events come back (after finding something that works like Ctrl + Z in Dev Tools with events).

[freezer2022]

jocelynetienne : it seems very doable to add also an "↩ Undo" button

The difference is that unlike in Element Picker wherein elements are hidden, in Element Zapper elements are removed.
Hidden elements can be easily restored (unhide), but removed elements cannot be easily recreated because the whole DOM structure of the website might dynamically change, and even if recreating is sometimes doable, in some other cases/websites it might be too problematic to recreate it.

[forthrin]

Suggestion: Wouldn't undo be good as follows?

1. User: Element Picker
2. uBlock: Adds rule to "My filters"
3. Browser: Removes the unintended thing
4. User: Undo
5. uBlock: Rule added in step 2 is removed from "My filters"
6. User: Reload page
7. Browser: Order is restored in the galaxy.

PS! A related aspect is when the unintended hiding was done long ago.

1. User: Goes to page
2. Browser: Shows page without wanted element

Question: Is there a more convenient method than the cumbersome:

3. User: Disable uBlock (for whole page)
4. User: Reload page
5. User: Find element with Element Picker or Developer Console
6. User: Find and delete corresponding rule in "My filters"
7. User: Enable uBlock
8. User: Reload page

[gorhill]

Is there a more convenient method than the cumbersome

• Hover mouse over cosmetic filtering switch in popup panel, this reveals number of hidden elements by cosmetic filters
• Toggle cosmetic filtering switch to make those hidden elements appear/disappear (no need to disable uBO)

Then if action is needed:

• Open logger
• Toggle DOM inspector (</>)
• Hidden elements will be highlighted, and corresponding cosmetic filters will be shown in DOM inspector

Ideally, maybe one day I will have time to implement the uBO Lite way, a "Remove a custom filter" approach.

Anyway, the topic here is about the zapper, it's an entirely different code path.

[forthrin]

Oh, Jesus! I never knew about this view (showing which rules hide what). This will make life (online at least) so much easier! Thanks a mill! I'll try out this newfound bliss before considering whether Undo (for Element Picker) is even necessary.