CODEWITHSUNDEEP
javascript
DrStrangeLove
DrStrangeLove

Reputation: 11557

JavaScript applications and empty HTML elements

JavaScript application often use one of the following methods:

  1. They use empty HTML elements (which exist in markup but are invisible because of display:none)
  2. They generate markup dynamically
  3. A combination of both

What is the best case for each of these methods? When should I prefer one over the other, and why?

Upvotes: 2

Views: 59

Answers (2)

Juan de Dios
Juan de Dios

Reputation: 2789

Things to considerate:

I choose A combination of both to optimize the load time.

Upvotes: 1

gen_Eric
gen_Eric

Reputation: 227240

It all depends on what you're trying to do.

If you want to add elements to a page, and you know how many you need, you can have them on the page and hide/show them when needed.

If you want to add a dynamic number of new elements, you can just make them on-the-fly, because having them on the page to begin with may not work if you need more than you added.

You can also clone existing elements, and change their attributes, to add elements to a page.

This all depends on what you're trying to do.

For example:

  1. You have a form that can accept a dynamic number of inputs. You don't know how many the user wants, so having them on the page to start with (hidden) won't help. You can either clone the existing inputs (and change their values), or create new ones and add them.
  2. You have a form that allows from 2-5 names to be added. Since there is a fixed amount, you can add 5 inputs, hide 3 of them to begin with, and show them if needed.

So, there are different methods for what you are trying to do.

Upvotes: 2

Related Questions