JSX vs HTML differences in React - When to Use Which

The Big Idea

Discover why mixing HTML and JavaScript the old way feels like juggling knives--and how JSX hands you a safer, sharper tool.

The Scenario

Imagine writing a web page by manually mixing JavaScript and HTML strings everywhere to update content dynamically.

You have to remember tiny syntax details and fix errors that break your page.

The Problem

Manually mixing HTML and JavaScript is confusing and easy to mess up.

Small mistakes like wrong attribute names or forgetting quotes cause bugs that are hard to find.

It slows down development and makes your code messy.

The Solution

JSX lets you write HTML-like code directly inside JavaScript with clear rules.

It fixes common HTML quirks by using JavaScript-friendly syntax, making your code easier to read and less error-prone.

Before vs After

✗ Before

element.innerHTML = '<div class="my-class">Hello</div>';
element.setAttribute('class', 'my-class');

✓ After

const element = <div className="my-class">Hello</div>;

What It Enables

JSX enables seamless, clear, and safe integration of UI structure with JavaScript logic for dynamic web apps.

Real Life Example

Building a user profile card that updates live as user data changes without juggling string concatenations or manual DOM updates.

Key Takeaways

Manual HTML in JavaScript is error-prone and hard to maintain.

JSX uses JavaScript-friendly syntax to write UI code clearly.

This makes building dynamic interfaces faster and less buggy.

Practice

1. Which attribute should you use in JSX to add CSS classes to an element?

easy

A. cssClass

B. class

C. className

D. styleClass

Solution

1. Step 1: Recall JSX attribute rules

   In JSX, the HTML attribute class is replaced by className because class is a reserved word in JavaScript.

2. Step 2: Identify correct attribute for CSS classes

   Therefore, to add CSS classes in JSX, you must use className.

3. Final Answer:

   className -> Option C

4. Quick Check:

   JSX uses className, not class [OK]

Hint: Remember: JSX uses className, not class for CSS classes [OK]

Common Mistakes:

• Using 'class' instead of 'className' causes errors
• Confusing 'className' with 'cssClass'
• Trying to use 'styleClass' which doesn't exist

2. Which of the following is the correct way to write a label with a 'for' attribute in JSX?

easy

A. Name

B. Name

C. Name

D. Name

Solution

1. Step 1: Understand JSX attribute naming

   In JSX, the HTML attribute for is replaced by htmlFor because for is a reserved word in JavaScript.

2. Step 2: Check correct casing and spelling

   The correct attribute is htmlFor with capital F, so <label htmlFor="inputId">Name</label> is correct.

3. Final Answer:

   <label htmlFor="inputId">Name</label> -> Option A

4. Quick Check:

   Use htmlFor, not for in JSX labels [OK]

Hint: Use htmlFor (camelCase) instead of for in JSX labels [OK]

Common Mistakes:

• Using 'for' attribute directly causes syntax errors
• Writing 'htmlfor' with lowercase f is incorrect
• Using non-existent attributes like 'forId'

3. What will be the rendered output of this JSX code?

const element = <input type="checkbox" checked="true" />;
ReactDOM.render(element, document.getElementById('root'));

medium

A. A checkbox input with checked attribute as string

B. A checked checkbox input

C. Syntax error due to checked attribute value

D. An unchecked checkbox input

Solution

1. Step 1: Analyze checked attribute in JSX

   In JSX, checked="true" without curly braces sets the prop to the string "true".

2. Step 2: Understand rendering of boolean attributes

   React renders <input type="checkbox" checked="true" />. Browsers treat the presence of the checked attribute (any non-empty value) as checked for uncontrolled checkboxes.

3. Final Answer:

   A checked checkbox input -> Option B

4. Quick Check:

   Attribute presence checks uncontrolled checkbox [OK]

Hint: checked="true" renders checked checkbox (attribute presence) [OK]

Common Mistakes:

• Thinking checked="true" leaves checkbox unchecked
• Expecting string value to cause syntax error
• Confusing uncontrolled render with controlled components

4. Identify the error in this JSX snippet:

const element = <div class="container">Hello</div>;

medium

A. Using class instead of className

B. Using double quotes instead of single quotes

C. Missing closing tag for div

D. Using semicolon inside JSX

Solution

1. Step 1: Check attribute names in JSX

   JSX does not use the HTML attribute class. Instead, it uses className because class is a reserved word in JavaScript.

2. Step 2: Verify other parts of the snippet

   The quotes and closing tag are correct. The semicolon is outside JSX and valid in JavaScript.

3. Final Answer:

   Using class instead of className -> Option A

4. Quick Check:

   JSX requires className, not class [OK]

Hint: Replace class with className in JSX attributes [OK]

Common Mistakes:

• Using class attribute causes React warnings or errors
• Thinking quotes style causes errors
• Confusing semicolon placement inside JSX

5. You want to apply inline styles to a JSX element to make text red and bold. Which is the correct way?

hard

A. Text

B. Text

C. Text

D. Text

Solution

1. Step 1: Understand JSX style attribute syntax

   In JSX, the style attribute expects a JavaScript object, so you use double curly braces: the outer for embedding JS, the inner for the object.

2. Step 2: Check property names and values

   CSS properties use camelCase in JSX, so fontWeight is correct. Values are strings like 'red' and 'bold'.

3. Final Answer:

   <div style={{color: 'red', fontWeight: 'bold'}}>Text</div> -> Option D

4. Quick Check:

   Use double braces and camelCase for inline styles [OK]

Hint: Use double braces and camelCase keys for JSX inline styles [OK]

Common Mistakes:

• Using string style attribute instead of object
• Missing curly braces around style object
• Using CSS property names with hyphens instead of camelCase