Outside of being concise, why would you want to use JavaScript instead of HTML to create the buttons?

Hi Alexandra,

Great question. Beyond being concise, there’s at least one other reason I’d personally consider using JS to create the buttons in this particular situation.

But first I’ll stress the importance of being concise. Consider an app/page that starts off with not just four list items, but with 100 list items. The amount of extra HTML you would have to code by hand (to add the buttons) would be pretty extreme in comparison.

But a reason outside of just being concise would be one of accessibility and user experience. Say for instance I have Javascript disabled in my browser (in this example I’m using a work computer or one from a library). Well if the buttons are hard coded into the HTML, then I have a set of buttons that show up on the page that suggests I can use them to change the order of (or delete) the buttons on the page, even though I would not be able to because of the limitations imposed on my browser. However, if the buttons are added via Javascript, then they only show up in cases where the browser will recognize and execute the Javascript code.

So when JS is disabled, only the list items show up and I have no idea that in some browsers users are able to move those items around or even delete them. And when JS is enabled, the buttons show up and work as seen in the video.

Does that offer any insight?

I’m sure there are other reasons you might would add all of those like buttons in JavaScript, but off the top of my head those would be the primary reasons for me choosing to do it that way.