If ‘IFs’ and Buts Were Candy…

We can program in such a way as to have our code make decisions for the end user. This logic can make for a better user experience and more intuitive program. One of the basic building blocks is an IF statement.

An IF statement decides whether something is true or false (boolean). Based upon the answer, appropriate code is run. Here is the basic syntax…

[code lang=”js”]
if(something is true){
// Then do something
}
[/code]

That’s it. That is all there is to it. The key is to remember that IF statements always test boolean…true/false…yes/no. Here is another example…

[code lang=”js”]
if(10 === 10{
alert(‘The tens are equal’);
}
[/code]

The aforementioned code would alert the end user that the tens were equal because it is true that 10 is equal to 10.

So that is one done with hard-coded values, but, typically, we use variables within our IF statements. Here is an example…

[code lang=”js”]
// Create variables to hold data
var firstNum = 10;
var secondNum = 10;
// Compare the two variables
if(firstNum === secondNum){
alert(‘The variables are equal’);
}
[/code]

So, as you can see, we can compare two variables to test whether the comparison is true or false. Over the next several posts, I will add more nuances to the IF statements. Before long, you will see how useful they can be.

Happy Coding!

Clay Hess

More To Explore

Code

A Quick Tour of the Web Encoding API

Modern web apps live at the boundary between JavaScript strings and raw bytes. The Web Encoding API exists to make that boundary explicit and safe: it lets you encode a string into UTF‑8 bytes and decode bytes back into text. Importantly, these operations aren’t symmetrical—encoding targets UTF‑8, while decoding can interpret UTF‑8 and many legacy encodings. Alongside the synchronous TextEncoder and TextDecoder, the platform also provides stream-based variants for processing text incrementally as data arrives.

Script Proofread And Sentence Grammar Spell Check
Code

EditContext API: A New Foundation for Custom Web Editors

The experimental EditContext API gives developers a new foundation for building custom rich text editors by separating text input and selection from rendering. Instead of relying on contenteditable, you attach an EditContext to a focusable element and manage your own text model, selection state, and UI updates—while still receiving browser-grade events for typing, caret movement, and IME composition. This demo highlights the core event flow and why character bounds matter for accurate input UI, especially in custom-rendered editors.

Share This Post

small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.