Is it correct to put an event inside an event?

Question

I have an script in which I'm going to add a file XLS, once that I validate the file format, I close a bootstrap's modal and open another modal which is an confirmation window to see whether the user is sure to upload that file.

This confirmation window has a confirmation button, once clicked I want that execute me an function which it's going to run an AJAX to make the request to the server.

However, because of that, I had the following doubts:

• Which of the 2 ways is better (and the most correct) to run the code and why?
• Why is the click event of the first input file executed if there has not been an event change? I mean, I add a file and the event change is executed and I can make clicks many times as I want, is not it supposed that I must add another file so that I can run the function inside again?
• Put an event inside an event, has it a name?

$(document).ready(function(){
  //First input file
  $(document).on('change','#file', function(){
    let file = $(this);
    let nameFile = file[0].files[0].name;
    let button = '<button type="button">Clic input 1</button>';
    
    $('#button').html(button);
    
    $('#button').click(function(){
      console.log('CLICK IN FIRST INPUT FILE!');
    });
    
  });
  
  //Second input file
  $(document).on('change','#file2', function(){
    let file = $(this);
    let nameFile = file[0].files[0].name;
    let button = '<button type="button">Clic input 2</button>';
    
    $('#button2').html(button);
  });
  
  $('#button2').click(function(){
      console.log('CLICK IN SECOND INPUT FILE!');
  });
  
});

<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
<input type="file" id="file" name="file" />
<div id="button"></div>

<div style="margin-top:20px"></div>

<input type="file" id="file2" name="file2"/>
<div id="button2"></div>

Answer 1

Put an event inside an event, has it a name?

It has, the name is Bad Idea. Let me Expain. What happens when you execute the following code.

$('#button').click(function(){
  console.log('CLICK IN FIRST INPUT FILE!');
});

A click event is registered to the button. Once an event is registered, it will fire everytime no matter how many times you click.

When you put that code inside another event handler like the first example, it gets executed everytime the file-input changes and a new event handler is registered. So when you select a file, and then decide to change it, file-input changes twice and you get 2 click events registered. Now click on the button, you get 2 new console log printed by one click!!! Try it..

Why is the click event of the first input file executed if there has not been an event change

Because that's how event handler works, you register once, they get fired everytime after that.

Which of the 2 ways is better (and the most correct) to run the code and why?

Obviously not the first one, because it is a bad idea, Not the second one either. In case of second one you are attaching event to a division that will contain the button. So you don't need to click on the button, just click anywhere right side of the button, the event gets fired!!!

So if none of them is right, what can we do?

• Do not generate button/any html element by javascript for such simple tasks. Do it with HTML, plain and simple.
• Do not nest event handler into another i.e put one event handler inside another, it will complicate things. Just put all event handlers directly inside document.ready event of jQuery. document.ready only fires once.
• When you need to control user action then show/hide your button or other html element by javascript based on required conditions.

My suggestion is doing something like this.

$(document).ready(function(){
    // Hide the button at first
    $('#button').hide();
    // When File-input changes
    $('#file').change(function(){
        if(**the file-input has a file selected**){
            $('#button').show();
        }
        else{
            $('#button').hide();
        }
    });
    // When Button Clicked
    $('#button').click(function(){
        // Do the action
    });
});

Answer 2

Which of the 2 ways is better (and the most correct) to run the code and why?

I believe this is better:

//Second input file
$(document).on('change','#file2', function(){
  let file = $(this);
  let nameFile = file[0].files[0].name;
  let button = '<button type="button">Clic input 2</button>';

  $('#button2').html(button);
});
$('#button2').click(function(){
  console.log('CLICK IN SECOND INPUT FILE!');
});

Mainly because it's more readable and easy to follow. There is no need to have the button click event set up AFTER the input has been changed. It is better to change the STATE of the button, as you are doing. Even better would be to hide/show the button like:

$('#button2').show();

And have it initially hidden with:

<div id="button2" style="display: none">Click me</div>

Why is the click event of the first input file executed if there has not been an event change?

In my test, this all worked correctly.

How is called this?

The change events should only be called when you click and assign a file to the input.

Answer 3

you are binding the same event multiple times to the same button object. binding the same event to the same object in another event that may reoccur will result in binding it over and over (stacks events and fire them and in this case "it" multiple times). binding an action to an event should happen only one time per object. and I see that you are binding the click event to the div instead of the button. maybe you need to consider dynamic binding using .on() like this

$(document).ready(function(){
  //first file change event
  $(document).on('change','#file', function(){
    let file = $(this);
    //handling empty selection
    if(file[0].files.length == 0){ 
        $('#button').html("");
        return;
    }
    let nameFile = file[0].files[0].name;
    let button = '<button type="button">Clic input 1</button>';
    
    $('#button').html(button);
  });
  //second file change event
  $(document).on('change','#file2', function(){
    let file = $(this);
    //handling empty selection
    if(file[0].files.length == 0){ 
        $('#button2').html("");
        return;
    }
    let nameFile = file[0].files[0].name;
    let button = '<button type="button">Clic input 2</button>';
    
    $('#button2').html(button);
  });
  
  //first button dynamic event (doesn't stack)
  $('#button').on('click','button', function(){
      console.log('CLICK IN FIRST INPUT FILE!');
    });
    
  //second button dynamic event (doesn't stack)
  $('#button2').on('click','button', function(){
      console.log('CLICK IN SECOND INPUT FILE!');
  });
  
});

<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
<input type="file" id="file" name="file" />
<div id="button"></div>

<div style="margin-top:20px"></div>

<input type="file" id="file2" name="file2"/>
<div id="button2"></div>

note that you need to handle not choosing a file (e.g. files count is 0) like in my code

Answer 4

Put an event inside an event, has it a name?

It does have a name. It's called "daisy chaining" and it's not a good idea.

Answer 5

not enough rep to comment

I've had cause to do this. I had the unpleasant task of mucking through 2 years of code written by one person with little maintenance or code discipline. I wanted to keep the code structure intact, so I daisy-chained click events to perform some enhancements.

To avoid some problems mentioned in the better answers above, simply remember to call $(selector).off("click") before binding the next event.

Answer 6

const mainevent = (e)=>{
e.preventDefault();
your event data
.then((e) => {
        second event()
      })
.catch((error) => 
      
      alert(error.message))
       }; 
}