How to block .remove() event

Question

I am writing a script for my client that already has some encrypted JavaScript. Somewhere in encrypted JavaScript there is .remove() event that trigger with a particular button. I found a script jQuery - Trigger event when an element is removed from the DOM that detect the .remove() event. After that i tried to block that event with this:

$('#fileElem').on('destroyed', function(){
    $('#fileElem').die('remove');                            
    $('input[name="done_upload"]').trigger('click');
});

But i got Uncaught TypeError: Object [object Object] has no method 'die' might be the destroyed event trigger after .remove() action, I am not sure. And as i used to auto trigger the button with $('input[name="done_upload"]').trigger('click'); not working because i got error before trigger event.

Can anyone help me to stop removing DOM element?

I seems to me that...once the destroyed event gets fired, the element is already gone so it's no use to intercept? — Bas Slagter, Oct 30 '13 at 12:11
you can decode javascript by using this URL: jsbeautifier.org — kwelsan, Oct 30 '13 at 12:12
What is the event that calls `remove()`, a `click`? Why not unbind the event and bind your own. — Boaz, Oct 30 '13 at 12:14
@jogesh_pi What I can think of is to add your own click handler to the same button and cancel out all others. But not sure if it works since that event can come later. — Bas Slagter, Oct 30 '13 at 12:15
@Boaz yes `click` event call .remove() and i am working with same `click()' event but separately — jogesh_pi, Oct 30 '13 at 12:16
you could clone the element and then reattach the clone after the click — Pete, Oct 30 '13 at 12:17
What about changing the ID of the particular button? Anyone wants to remove it, will fail silently. — ern0, Oct 30 '13 at 12:34

Joseph · Answer 1 · 2013-10-30T12:28:34.567

4

.die() is filed under the removed section of jQuery, so unless if you are using an older version of jQuery (like <1.8), it doesn't exist anymore. That's what's causing that thrown error.

This fiddle (loaded with 1.9) alerts false while testing for .die(), which means it does not exist. If you use 1.8.3 or earlier though, it will alert true which means it's still there.

If you want to prevent the removal of that element, I suggest you "hijack" (replace) the button's click handler instead.

edited Oct 30 '13 at 12:28

answered Oct 30 '13 at 12:13

Joseph

117,725
30
181
234

1

It's probably worth mentioning that he can refer to the element as `$(this)` inside the event handler, as it may no longer be accessible via DOM parsing (unlikely, I know, but worth him knowing). – Reinstate Monica Cellio Oct 30 '13 at 12:19
@Archer but a jQuery object, regardless if it has fetched anything on the DOM, will still have it's prototype functions. Doing `$('#foo').remove().die().off()` with no `#foo` existing will not throw an error. – Joseph Oct 30 '13 at 12:25
1

Yeah, but it may not return anything is my point, whereas `this` will still be a reference to the object. Like I said, it's unlikely, but there's really no harm in explaining the use of `this` to the OP. – Reinstate Monica Cellio Oct 30 '13 at 12:27

score 2 · Answer 2 · edited Oct 30 '13 at 12:34

2

I think that destroyed event is fired when element is already destroyed so you get an empty jQuery query result.

edited Oct 30 '13 at 12:34

shanabus

12,989
6
52
78

answered Oct 30 '13 at 12:12

Romko

1,808
21
27

How to block .remove() event

2 Answers2