Objects

nametag badges

JavaScript objects are a way to elegantly combine data and actions together in an object-oriented manner. The possibilities are endless. Think of having arrays that can sort themselves or strings that can search themselves.

Additionally, objects allow us to think in terms of things as opposed to data and actions. We can more emulate the real world.

Data within an object is accessible to the functions but hidden to the outside world. The outer world only sees what the object wants it to see (encapsulation). The object serves as a container that stores data and links it to code that can take action on it.

Data within an object is referred to as object members. So within objects…

  • variables are properties
  • functions are called methods

We can access each of these using dot-object notation…

object.property

object.method

Here is an example…

var person = {
    firstName: "Joe",
    lastName: "Schmoe",
    age: 50,
    talk: function(){
        return "Hello, my name is " + this.firstName + " " + this.lastName;
    }
}

We can access this object with the dot-object notation as follows…

person.firstName; // Should output Joe
person.talk(); // Should output "Hello, my name is Joe Schmoe"

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.